Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-23326

Implement a ProcedureStore which stores procedures in a HRegion

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • None
    • 3.0.0-alpha-1, 2.3.0
    • proc-v2
    • None
    • Reviewed
    • Hide
      Use a region based procedure store to replace the old customized WAL based procedure store. The procedure data migration is done automatically during upgrading. After upgrading, the MasterProcWALs directory will be deleted and a new MasterProc directory will be created. And notice that a region will still write WAL so we still have WAL files and they will be moved to the oldWALs directory. The file name is mostly like a normal WAL file, and the only difference is that it is ended with "$masterproc$".
      Show
      Use a region based procedure store to replace the old customized WAL based procedure store. The procedure data migration is done automatically during upgrading. After upgrading, the MasterProcWALs directory will be deleted and a new MasterProc directory will be created. And notice that a region will still write WAL so we still have WAL files and they will be moved to the oldWALs directory. The file name is mostly like a normal WAL file, and the only difference is that it is ended with "$masterproc$".

    Description

      So we can resue the code in HRegion for persisting the procedures, and also the optimized WAL implementation for better performance.

      This requires we merge the hbase-procedure module to hbase-server, which is an anti-pattern as we make the hbase-server module more overloaded. But I think later we can first try to move the WAL stuff out.

      Attachments

        Issue Links

          There are no Sub-Tasks for this issue.

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: