HBase
  1. HBase
  2. HBASE-7271

Have a single executor for all zkWorkers in the assignment manager

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.95.2
    • Fix Version/s: 0.95.0
    • Component/s: master, Region Assignment
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      The current strategy is to have an array of monothreaded executor, and hash the zk path to ensure that there are no two events on the same region executed in parallel

      I think a single executor, as presented in the attached patch, is better because:

      • we're guaranteed to use all threads at any time
      • if managing one of the event takes longer that expected, the slowness is limited to this region, and not to all regions that have the same hashed/moduloed code
      • For the nodeChildrenChanged, there is no need to choose randomly one of the worker (or, once again, the risk to get stuck if one of the event takes time to be managed).
      1. 7271.v1.patch
        8 kB
        Nicolas Liochon
      2. 7271.v2.patch
        9 kB
        Nicolas Liochon
      3. 7271.v2.patch
        9 kB
        Nicolas Liochon
      4. 7271.v3.patch
        9 kB
        Nicolas Liochon

        Issue Links

          Activity

            People

            • Assignee:
              Nicolas Liochon
              Reporter:
              Nicolas Liochon
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development