Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 24 May 2017 23:46:04 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13074686.1495669550000.289221.1495669564416@Atlassian.JIRA>
In-Reply-To: <JIRA.13074686.1495669550000@Atlassian.JIRA>
References: <JIRA.13074686.1495669550000@Atlassian.JIRA> <JIRA.13074686.1495669550811@jira-lw-us.apache.org>
Subject: [jira] [Created] (HBASE-18105) [AMv2] Split/Merge need cleanup;
 currently they diverge and do not fully embrace AMv2 world
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 24 May 2017 23:46:09 -0000

stack created HBASE-18105:
-----------------------------

             Summary: [AMv2] Split/Merge need cleanup; currently they diver=
ge and do not fully embrace AMv2 world
                 Key: HBASE-18105
                 URL: https://issues.apache.org/jira/browse/HBASE-18105
             Project: HBase
          Issue Type: Sub-task
          Components: Region Assignment
    Affects Versions: 2.0.0
            Reporter: stack


Region Split and Merge work on the new AMv2 but they work differently. This=
 issue is about bringing them back together and fully embracing the AMv2 pr=
ogram.

They both have issues mostly the fact that they carry around baggage no lon=
ger necessary in the new world of assignment.

Here are some of the items:

Split and Merge metadata modifications are done by the Master now but we ha=
ve vestige of Split/Merge on RS still; e.g. when we SPLIT, we ask the Maste=
r which asks the RS, which turns around, and asks the Master to run the ope=
ration. Fun. MERGE is all done Master-side.
=20
Clean this up. Remove asking RS to run SPLIT and remove RegionMergeRequest,=
 etc. on RS-side. Also remove PONR. We don=E2=80=99t Points-Of-No-Return no=
w we are up on Pv2. Remove all calls in Interfaces; they are unused. Make R=
S still able to detect when split, but have it be a client of Master like a=
nyone else.

Split is Async but does not return procId

Split is async. Doesn=E2=80=99t return the procId though. Merge does. Fix. =
Only hard part here I think is the Admin API does not allow procid return.

Flags

Currently OFFLINE is determined by looking either at the master instance of=
 HTD (isOffline) and/or at the RegionState#state. Ditto for SPLIT. For MERG=
E, we rely on RegionState#state. Related is a note above on how split works=
 -- there is a split flag in HTD when there should not be.
=20
TODO is move to rely on RegionState#state exclusively in Master.

From Split/Merge Procedures need finishing in https://docs.google.com/docum=
ent/d/1eVKa7FHdeoJ1-9o8yZcOTAQbv0u0bblBlCCzVSIn69g/edit#heading=3Dh.4b60dc1=
h4m1f


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)