hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18491) [AMv2] Fail UnassignProcedure if source Region Server is not online.
Date Wed, 02 Aug 2017 03:55:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110244#comment-16110244
] 

Hudson commented on HBASE-18491:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-2.0 #276 (See [https://builds.apache.org/job/HBase-2.0/276/])
HBASE-18491 [AMv2] Fail UnassignProcedure if source Region Server is not (stack: rev 3f540f3801c93813a3a018dddb7fdf24d4aff27d)
* (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)

Mime
View raw message