hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-4402) Retaining locality after restart broken
Date Thu, 06 Oct 2011 20:13:30 GMT

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

stack updated HBASE-4402:
-------------------------

    Attachment: 4402-v3.txt

Here is what I committed (Todd's work plus the little amendment).
                
> Retaining locality after restart broken
> ---------------------------------------
>
>                 Key: HBASE-4402
>                 URL: https://issues.apache.org/jira/browse/HBASE-4402
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 0.92.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>             Fix For: 0.92.0
>
>         Attachments: 4402-v3.txt, hbase-4402.txt, hbase-4402.txt
>
>
> In DefaultLoadBalancer, we implement the "retain assignment" function like so:
> {code}
>       if (sn != null && servers.contains(sn)) {
>         assignments.get(sn).add(region.getKey());
> {code}
> but this will never work since after a cluster restart, all servers have a new ServerName
with a new startcode.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message