[ https://issues.apache.org/jira/browse/HBASE-22767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16948137#comment-16948137 ]
Hudson commented on HBASE-22767: -------------------------------- Results for branch branch-2 [build #2317 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2317/]: (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/2317//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/2317//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/branch-2/2317//JDK8_Nightly_Build_Report_(Hadoop3)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. (/) {color:green}+1 client integration test{color} > System table RIT STUCK if their RSGroup has no highest version RSes > ------------------------------------------------------------------- > > Key: HBASE-22767 > URL: https://issues.apache.org/jira/browse/HBASE-22767 > Project: HBase > Issue Type: Bug > Components: rsgroup > Reporter: Xiaolin Ha > Assignee: Xiaolin Ha > Priority: Major > Fix For: 3.0.0, 2.3.0, 2.2.2 > > > AM chooses highest version region servers as participants for system tables, > including META table. If system table group has no highest version region > servers, then the reassignment of their regions will be always the BOGUS > server defined in RSGroup. > In our test environment using branch-2.2, we isolate system tables in a > rsgroup containing only one server. And when upgrading RSs, we have met the > problem that META is always assigned to the BOGUS server while the group > server has already been online for a while. META RIT is stuck and can not be > recovered by hbck2. > I made a UT reproduce this problem, steps are: > 1. add a group, move 1 server to it; > 2. move meta table to the group; > 3. restart the group server and downgrade its version; > 4. meta rit stuck. > > ROOT cause is AM filters highest version RSs for system tables. So if we do > not change the versions of system table group servers, but upgrade the > versions of other group servers, then if there is reassignment for any system > tables, such as balancer moving their regions, RIT STUCK!! > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)