[
https://issues.apache.org/jira/browse/HBASE-18493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129224#comment-16129224
]
Hudson commented on HBASE-18493:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3544 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3544/])
HBASE-18493 [AMv2] Skipped re-assignment of regions on crashed server (stack:
rev acf9b87dca2cd190f4b5318efd5dc48e19b317f4)
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/AssignmentManager.java
> [AMv2] On region server crash do not process system table regions through
> AssignmentManager.checkIfShouldMoveSystemRegionAsync()
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-18493
> URL: https://issues.apache.org/jira/browse/HBASE-18493
> Project: HBase
> Issue Type: Bug
> Components: amv2
> Affects Versions: 2.0.0
> Reporter: Umesh Agashe
> Assignee: Umesh Agashe
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: hbase-18493.master.001.patch
>
>
> On Region Server crash, as ServerCrashProcedure handles reassignment of all
> the regions on a crashed server, don't process those regions through
> AssignmentManager.checkIfShouldMoveSystemRegionAsync(). This avoids duplicate
> and makes ServerCrashProcedure as one place to find all related code for
> handling server crash.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
