[
https://issues.apache.org/jira/browse/HBASE-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182568#comment-15182568
]
Mikhail Antonov commented on HBASE-15406:
-----------------------------------------
I guess Ted is talking about the latter case, when you start hbck, then decide
you need to re-run it with different set of arguments and hit ctrl+c, then you
get distracted by something (or loose network connection, or something). That
shouldn't leave the cluster in the bad shape.
One of the solutions would be to have ephemeral znode for hbck and a chore on
master which keeps track of it. Adding yet more stuff to ZK, but conceptually I
won't see the problem here - we don't want to keep more configuration
properties there, but keeping transient state is probably fine.
> 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
> Fix For: 2.0.0, 1.3.0, 1.4.0
>
>
> 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)
