[
https://issues.apache.org/jira/browse/HBASE-21683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737344#comment-16737344
]
Hudson commented on HBASE-21683:
--------------------------------
Results for branch branch-2.0
[build #1236 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1236/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1236//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1236//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.0/1236//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
> Reset readsEnabled flag after successfully flushing the primary region
> ----------------------------------------------------------------------
>
> Key: HBASE-21683
> URL: https://issues.apache.org/jira/browse/HBASE-21683
> Project: HBase
> Issue Type: Bug
> Components: read replicas
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Critical
> Fix For: 3.0.0, 2.2.0, 2.1.3, 2.0.5
>
> Attachments: HBASE-21683.patch, HBASE-21683.patch
>
>
> Found the problem when implementing HBASE-21671, TestRegionReplicaFailover is
> easy to fail. In this test we set
> REGION_REPLICA_WAIT_FOR_PRIMARY_FLUSH_CONF_KEY to true, which means the
> secondary replicas can not be read until the primary region has been
> successfully flushed. But in RegionReplicaFlushHandler, there is only one
> place where we call region.setReadsEnabled(true), this is incorrect.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
