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

Add voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    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

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            zhangduo Duo Zhang

            Dates

              Created:
              Updated:

              Slack

                Issue deployment