Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 7 Jun 2016 22:08:21 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12947524.1457279388000.20621.1465337301076@Atlassian.JIRA>
In-Reply-To: <JIRA.12947524.1457279388000@Atlassian.JIRA>
References: <JIRA.12947524.1457279388000@Atlassian.JIRA> <JIRA.12947524.1457279388180@arcas>
Subject: [jira] [Commented] (HBASE-15406) Split / merge switch left disabled
 after early termination of hbck
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 07 Jun 2016 22:08:23 -0000


    [ https://issues.apache.org/jira/browse/HBASE-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319552#comment-15319552 ] 

Enis Soztutar commented on HBASE-15406:
---------------------------------------

[~syuanjiang] and I was discussing this offline. One idea that he was proposing is to re-purpose the HBCK lock into being a znode lock, and have the CJ, Balancer and Split/Merge look into whether HBCK is running or not. I think this will be much simpler than adding 3 "advanced" APIs to Admin.  wdyt?

> Split / merge switch left disabled after early termination of hbck
> ------------------------------------------------------------------
>
>                 Key: HBASE-15406
>                 URL: https://issues.apache.org/jira/browse/HBASE-15406
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Heng Chen
>            Priority: Critical
>              Labels: reviewed
>             Fix For: 2.0.0, 1.3.0, 1.4.0
>
>         Attachments: HBASE-15406.patch, HBASE-15406.v1.patch, HBASE-15406_v1.patch, HBASE-15406_v2.patch, test.patch, wip.patch
>
>
> This was what I did on cluster with 1.4.0-SNAPSHOT built Thursday:
> Run 'hbase hbck -disableSplitAndMerge' on gateway node of the cluster
> Terminate hbck early
> Enter hbase shell where I observed:
> {code}
> hbase(main):001:0> splitormerge_enabled 'SPLIT'
> false
> 0 row(s) in 0.3280 seconds
> hbase(main):002:0> splitormerge_enabled 'MERGE'
> false
> 0 row(s) in 0.0070 seconds
> {code}
> Expectation is that the split / merge switches should be restored to default value after hbck exits.


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