hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18246) Proc-V2 AM: Maintain Data locality in ServerCrashProcedure
Date Wed, 16 Aug 2017 16:56:00 GMT

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

stack commented on HBASE-18246:

Is this a problem still [~syuanjiang]?

> Proc-V2 AM: Maintain Data locality in ServerCrashProcedure
> ----------------------------------------------------------
>                 Key: HBASE-18246
>                 URL: https://issues.apache.org/jira/browse/HBASE-18246
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Region Assignment
>    Affects Versions: 2.0.0
>            Reporter: Stephen Yuan Jiang
>            Assignee: Stephen Yuan Jiang
>            Priority: Critical
>             Fix For: 2.0.0
> Before HBASE-18036, SSH would use round-robin to re-distribute regions during processing.
 Round-robin assignment would loss data locality.  HBASE-18036 retains data locality if the
dead region server has already restarted when the dead RS is processing.  
> With Proc-V2 based AM, the change of HBASE-18036 in Apache HBASE 1.x releases is no longer
possible.  We need to implement the same logic under Proc-V2 based AM.

This message was sent by Atlassian JIRA

View raw message