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

Confirm that we can (rolling) upgrade from 2.0.x and 2.1.x to 2.2.x after HBASE-20881

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • None
    • 2.1.1, 2.0.3
    • amv2, proc-v2
    • None
    • Reviewed
    • Hide
      hbase-2.2.x uses a new Procedure form assiging/unassigning/moving Regions; it does not process hbase-2.1.x and earlier Unassign/Assign Procedure types. Upgrade requires that we first drain the Master Procedure Store of old style Procedures before starting the new 2.2.x Master. The patch here facilitates the draining process.

      On your running hbase-2.1.1+ (or 2.0.3+ cluster), when upgrading:

      1. Shutdown both active and standby masters (Your cluster will continue to server reads and writes without interruption).
      2. Set the property hbase.procedure.upgrade-to-2-2 to true in hbase-site.xml for the Master, and start only one Master, still using the 2.1.1+ (or 2.0.3+) binaries.
      3. Wait until the Master quits. Confirm that there is a 'READY TO ROLLING UPGRADE' message in the master log as the cause of the shutdown. The Procedure Store is now empty.
      4. Start new Masters with the new 2.2.0+ code.
      Show
      hbase-2.2.x uses a new Procedure form assiging/unassigning/moving Regions; it does not process hbase-2.1.x and earlier Unassign/Assign Procedure types. Upgrade requires that we first drain the Master Procedure Store of old style Procedures before starting the new 2.2.x Master. The patch here facilitates the draining process. On your running hbase-2.1.1+ (or 2.0.3+ cluster), when upgrading: 1. Shutdown both active and standby masters (Your cluster will continue to server reads and writes without interruption). 2. Set the property hbase.procedure.upgrade-to-2-2 to true in hbase-site.xml for the Master, and start only one Master, still using the 2.1.1+ (or 2.0.3+) binaries. 3. Wait until the Master quits. Confirm that there is a 'READY TO ROLLING UPGRADE' message in the master log as the cause of the shutdown. The Procedure Store is now empty. 4. Start new Masters with the new 2.2.0+ code.

    Attachments

      Issue Links

        relates to

        Sub-task - The sub-task of the issue HBASE-20881 Introduce a region transition procedure to handle all the state transition for a region

        • Major - Major loss of function.
        • Resolved

        Sub-task - The sub-task of the issue HBASE-21970 Document that how to upgrade from 2.0 or 2.1 to 2.2+

        • Major - Major loss of function.
        • Resolved

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: