hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-18493) [AMv2] On region server crash do not process system table regions through AssignmentManager.checkIfShouldMoveSystemRegionAsync()
Date Wed, 16 Aug 2017 15:14:00 GMT

     [ https://issues.apache.org/jira/browse/HBASE-18493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-18493:
--------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Pushed. Thanks [~uagashe]

> [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