Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-14350 Procedure V2 Phase 2: Assignment Manager
  3. HBASE-18107

[AMv2] Remove DispatchMergingRegionsRequest & DispatchMergingRegions

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.0.0-alpha-1
    • 2.0.0
    • Region Assignment
    • None
    • Reviewed
    • Hide
      Removes merge region code added into branch-2 but that was not needed after all. Branch-2 replaced dispatchMergingRegions with MergeTableRegionsProcedure.

      Removed:

      # dispatchMergingRegions from Connection (was superceded long ago in branch-1).
      # mergeRegions from RsRpcServices (was not used).
      Show
      Removes merge region code added into branch-2 but that was not needed after all. Branch-2 replaced dispatchMergingRegions with MergeTableRegionsProcedure. Removed: # dispatchMergingRegions from Connection (was superceded long ago in branch-1). # mergeRegions from RsRpcServices (was not used).

    Description

      They don't align with how we have named the Split equivalents; i.e. SplitRegion (so should be MergeRegion...). They probably have these awkward names because the obvious slots are occupied... so this may not be fixable but filing issue anyways.

      Attachments

        1. draft.patch
          542 kB
          Yi Liang
        2. hbase-18107-master.v1.patch
          541 kB
          Yi Liang
        3. HBASE-18107-master-v2.patch
          542 kB
          Yi Liang

        Issue Links

        Activity

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

          People

            easyliangjob Yi Liang
            stack Michael Stack
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment