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] [Updated] (HBASE-16941) FavoredNodes - Split/Merge code paths
Date Sat, 03 Dec 2016 01:25:58 GMT

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

Thiruvel Thirumoolan updated HBASE-16941:
    Attachment: HBASE-16941.master.011.patch

> FavoredNodes - Split/Merge code paths
> -------------------------------------
>                 Key: HBASE-16941
>                 URL: https://issues.apache.org/jira/browse/HBASE-16941
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Thiruvel Thirumoolan
>            Assignee: Thiruvel Thirumoolan
>             Fix For: 2.0.0
>         Attachments: HBASE-16941.master.001.patch, HBASE-16941.master.002.patch, HBASE-16941.master.003.patch,
HBASE-16941.master.004.patch, HBASE-16941.master.005.patch, HBASE-16941.master.006.patch,
HBASE-16941.master.007.patch, HBASE-16941.master.008.patch, HBASE-16941.master.009.patch,
HBASE-16941.master.010.patch, HBASE-16941.master.011.patch
> This jira is to deal with the split/merge logic discussed as part of HBASE-15532. The
design document can be seen at HBASE-15531. The specific changes are:
> Split and merged regions should inherit favored node information from parent regions.
For splits also include some randomness so even if there are subsequent splits, the regions
will be more or less distributed. For split, we include 2 FN from the parent and generate
one random node.

This message was sent by Atlassian JIRA

View raw message