Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 15 Jun 2016 04:18:09 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12947524.1457279388000.661.1465964289386@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: Wed, 15 Jun 2016 04:18:11 -0000


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

stack commented on HBASE-15406:
-------------------------------

Sorry. Late to the reply.

My -1 comment was against a system that had a tool set a state that master would cleanup under certain conditions. I was against complicating the master role to deal with weird tooling behaviors. To keep things manageable and contained, I suggested let the tool do the fix up/clean up.

Enis shows up with a general category under which we could gather a fleet of operation types that could impinge on master state that keeps-it-simple for the master. I'm in favor of his suggestion.

Sorry if I ended up making more work for you [~chenheng]

> 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
>              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)