[
https://issues.apache.org/jira/browse/HBASE-18491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110302#comment-16110302
]
Hudson commented on HBASE-18491:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3477 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3477/])
HBASE-18491 [AMv2] Fail UnassignProcedure if source Region Server is not
(stack: rev ba5e8706dee615357222ab652fcc9bc2a1923a94)
* (edit)
hbase-server/src/test/java/org/apache/hadoop/hbase/master/procedure/TestServerCrashProcedure.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/UnassignProcedure.java
> [AMv2] Fail UnassignProcedure if source Region Server is not online.
> --------------------------------------------------------------------
>
> Key: HBASE-18491
> URL: https://issues.apache.org/jira/browse/HBASE-18491
> 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-18491.master.001.patch
>
>
> Currently UnassignProcedure returns success when server carrying a region is
> NOT online. Assumption here is that ServerCrashProcedure will handle
> splitting logs etc for these regions. When UnassignProcedure completes,
> MoveRegionProcedure resumes with AssignProcedure. AssignProcedure can some
> times assign regions without pre-requisite steps (done either by
> UnassignProcedure or ServerCrashProcedure). Fix is to fail UnassignProcedure
> and parent MoveRegionProcedure if source server is not online.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)