Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-20828 Finish-up AMv2 Design/List of Tenets/Specification of operation
  3. HBASE-21395

Abort split/merge procedure if there is a table procedure of the same table going on



    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.0, 2.0.2
    • Fix Version/s: 2.0.3, 2.1.2
    • Component/s: None
    • Labels:


      In my ITBLL, I often see that if split/merge procedure and table procedure(like ModifyTableProcedure) happen at the same time, and since there some race conditions between these two kind of procedures, causing some serious problems. e.g. the split/merged parent is bought on line by the table procedure or the split merged region making the whole table procedure rollback.
      Talked with [~Apache9] offline today, this kind of problem was solved in branch-2+ since There is a fence that only one RTSP can agianst a single region at the same time.
      To keep out of the mess in branch-2.0 and branch-2.1, I added a simple safe fence in the split/merge procedure: If there is a table procedure going on against the same table, then abort the split/merge procedure. Aborting the split/merge procedure at the beginning of the execution is no big deal, compared with the mess it will cause...


        1. HBASE-21395.branch-2.0.001.patch
          4 kB
          Allan Yang
        2. HBASE-21395.branch-2.0.002.patch
          5 kB
          Allan Yang
        3. HBASE-21395.branch-2.0.003.patch
          7 kB
          Allan Yang
        4. HBASE-21395.branch-2.0.004.patch
          6 kB
          Allan Yang

          Issue Links



              • Assignee:
                allan163 Allan Yang
                allan163 Allan Yang
              • Votes:
                0 Vote for this issue
                4 Start watching this issue


                • Created: