[
https://issues.apache.org/jira/browse/HBASE-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16531331#comment-16531331
]
Hudson commented on HBASE-20830:
--------------------------------
Results for branch master
[build #385 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/385/]: (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/master/385//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/master/385//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/385//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Document that region replica does not work well with AMv2
> ---------------------------------------------------------
>
> Key: HBASE-20830
> URL: https://issues.apache.org/jira/browse/HBASE-20830
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20830.patch
>
>
> As we can see lots of TODOs for region replica feature in the
> AssignmentManager' code. And also, now we rely on the openSeqNum to determine
> whether a region has been successfully reopened, but the openSeqNum for a
> non-default replica region seems unstable...
> It is too late for the 2.1.0 release so let's just add a note in ref guide to
> say that region replica does not work well with AMv2 first, and then start to
> make it stable in follow on minor or major release lines.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
