Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 17 Jun 2016 20:33:05 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12980301.1466195264000.26845.1466195585298@Atlassian.JIRA>
In-Reply-To: <JIRA.12980301.1466195264000@Atlassian.JIRA>
References: <JIRA.12980301.1466195264000@Atlassian.JIRA> <JIRA.12980301.1466195264310@arcas>
Subject: [jira] [Updated] (HBASE-16059) Region normalizer failed to trigger
 merge action where expected
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 17 Jun 2016 20:33:07 -0000


     [ https://issues.apache.org/jira/browse/HBASE-16059?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu updated HBASE-16059:
---------------------------
    Status: Patch Available  (was: Open)

> Region normalizer failed to trigger merge action where expected
> ---------------------------------------------------------------
>
>                 Key: HBASE-16059
>                 URL: https://issues.apache.org/jira/browse/HBASE-16059
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>            Reporter: Romil Choksi
>            Assignee: Ted Yu
>              Labels: normalization
>             Fix For: 2.0.0
>
>         Attachments: 16059.v1.txt
>
>
> Region normalizer failed to trigger merge action where expected
> Steps to reproduce:
> - Pre-split the test table into 5 regions with keys 1,3,7,8
> - Insert some data for each of the split. 27K rows for regions starting w=
ith key 1, and 100K rows for each of the regions with start key 3,7 and 8
> - Scan the test table, and verify that these regions exists -  1) STARTKE=
Y =3D> =E2=80=98' ENDKEY =3D> =E2=80=991=E2=80=99  2)  STARTKEY =3D> =E2=80=
=991=E2=80=99 ENDKEY =3D> =E2=80=993=E2=80=99
> - Turn on normalization, verify normalization switch is enabled and that =
normalization is true for test table
> - Run normalizer a few times
> - Scan test table again, verify that regions don=E2=80=99t exist anymore =
 1) STARTKEY =3D> =E2=80=98' ENDKEY =3D> =E2=80=991=E2=80=99  2)  STARTKEY =
=3D> =E2=80=991=E2=80=99 ENDKEY =3D> =E2=80=993=E2=80=99, but instead a new=
 region is created with  STARTKEY =3D> =E2=80=99=E2=80=99 ENDKEY =3D> =E2=
=80=993=E2=80=99
> The test now fails, with the last step failing at assertion.=20
> Looking into the Master log, I see that normalization plan was computed f=
or the test table but it decides that no normalization is needed for the te=
st table, and that the regions look good.
> {code:title =3D Master.log}
> 2016-06-17 00:41:46,895 DEBUG [B.defaultRpcServer.handler=3D4,queue=3D1,p=
ort=3D20000] normalizer.SimpleRegionNormalizer: Computing normalization pla=
n for table: table_zrof6ea383, number of regions: 5
> 2016-06-17 00:41:46,895 DEBUG [B.defaultRpcServer.handler=3D4,queue=3D1,p=
ort=3D20000] normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, tot=
al aggregated regions size: 13
> 2016-06-17 00:41:46,896 DEBUG [B.defaultRpcServer.handler=3D4,queue=3D1,p=
ort=3D20000] normalizer.SimpleRegionNormalizer: Table table_zrof6ea383, ave=
rage region size: 2.6
> 2016-06-17 00:41:46,896 DEBUG [B.defaultRpcServer.handler=3D4,queue=3D1,p=
ort=3D20000] normalizer.SimpleRegionNormalizer: No normalization needed, re=
gions look good for table: table_zrof6ea383
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)