hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiruvel Thirumoolan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17620) Move table to another group (add -migrateTertiary)
Date Thu, 09 Feb 2017 20:47:42 GMT

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

Thiruvel Thirumoolan commented on HBASE-17620:

[~toffer]/[~devaraj] - What do you think?

> Move table to another group (add -migrateTertiary)
> --------------------------------------------------
>                 Key: HBASE-17620
>                 URL: https://issues.apache.org/jira/browse/HBASE-17620
>             Project: HBase
>          Issue Type: Sub-task
>          Components: FavoredNodes
>            Reporter: Thiruvel Thirumoolan
>            Assignee: Thiruvel Thirumoolan
>             Fix For: 2.0.0
> As part of the design document in HBASE-15531, we mentioned about an approach to move
tables to new group. First only one favored node would be moved to the new group using something
like "rpm -migrateTertiary" command (this will be something else since RPM will be deprecated).
Once enough locality has builtup on the tertiary nodes, the table can be moved to the group.
> In my experience, the likelihood of tables moving across groups is rare and there is
a brief amount of time when one of the FN will belong to another group and stuff like that.
When regions split, we also have to consider this situation and generate one FN from the target
(or tertiary's) group.
> Is this feature required? Do we need this as a start? I can attach tentative patches
and we could reconsider this in future if we don't need this as a start.

This message was sent by Atlassian JIRA

View raw message