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-18493) [AMv2] On region server crash do not process system table regions through AssignmentManager.checkIfShouldMoveSystemRegionAsync()
Date Wed, 16 Aug 2017 18:14:00 GMT

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

Hudson commented on HBASE-18493:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-2.0 #341 (See [https://builds.apache.org/job/HBase-2.0/341/])
HBASE-18493 [AMv2] Skipped re-assignment of regions on crashed server (stack: rev 53c5bcc5827217bfa05136bd14b78fde93529783)
* (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)

Mime
View raw message