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

Merge the update procedure store on locking with the general persist after a procedure execution

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Open
    • Critical
    • Resolution: Unresolved
    • None
    • None
    • amv2, Performance
    • None

    Description

      For each procedure step, we now update the store twice; once to persist lock state and then later to persist the change in the procedure's dataset. Writing the store is the long-pole in procedure operation. Can we unify the two steps? (It is awkward because currently second persist is done outside of lock because it slow... and then updating lock state must be done inside lock else....). TODO!

      Attachments

        Issue Links

          breaks

          Sub-task - The sub-task of the issue HBASE-21384 Procedure with holdlock=false should not be restored lock when restarts

          • Blocker - Blocks development and/or testing work, production could not run
          • Resolved
          is related to

          Sub-task - The sub-task of the issue HBASE-20846 Restore procedure locks when master restarts

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              zhangduo Duo Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: