HBase
  1. HBase
  2. HBASE-4402

Retaining locality after restart broken

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.92.0
    • Fix Version/s: 0.92.0
    • Component/s: master
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      In DefaultLoadBalancer, we implement the "retain assignment" function like so:

            if (sn != null && servers.contains(sn)) {
              assignments.get(sn).add(region.getKey());
      

      but this will never work since after a cluster restart, all servers have a new ServerName with a new startcode.

      1. hbase-4402.txt
        7 kB
        Todd Lipcon
      2. hbase-4402.txt
        8 kB
        Todd Lipcon
      3. 4402-v3.txt
        8 kB
        stack

        Activity

        Todd Lipcon created issue -
        Todd Lipcon made changes -
        Field Original Value New Value
        Assignee Todd Lipcon [ tlipcon ]
        Todd Lipcon made changes -
        Attachment hbase-4402.txt [ 12494575 ]
        Todd Lipcon made changes -
        Status Open [ 1 ] Patch Available [ 10002 ]
        Todd Lipcon made changes -
        Attachment hbase-4402.txt [ 12494670 ]
        stack made changes -
        Attachment 4402-v3.txt [ 12498062 ]
        stack made changes -
        Status Patch Available [ 10002 ] Resolved [ 5 ]
        Hadoop Flags Reviewed [ 10343 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Todd Lipcon
            Reporter:
            Todd Lipcon
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development