hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15406) Split / merge switch left disabled after early termination of hbck
Date Mon, 13 Jun 2016 19:30:30 GMT

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

Mikhail Antonov commented on HBASE-15406:

[~enis] [~chenheng] [~stack] this patch is addressing real problem, but I agree that all solutions
discussed above so far had their shortcomings.

I don't really want this jira to hold off 1.3 release if possible, so I'd be fine to revert
is from 1.3 and reduce it from Critical to Major. With the reasoning that from operational
standpoint, hitting Ctrl-C while running HBCK is preventable mis-command, prod clusters should
have scheduled and frequent HBCK runs anyway, and if your scheduled HBCK crashes (not reporting
inconsistencies, but crashes so that switches aren't restored) you have bigger problems.


> 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

View raw message