[
https://issues.apache.org/jira/browse/HBASE-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Law updated HBASE-14092:
------------------------------
Attachment: HBASE-14092-v2.patch
By default, hbck is run in a read-only checker mode. In this case, it is
sensible to let others run. By default, the balancer is left alone,
which may cause spurious errors, but cannot leave the balancer in a bad
state. It is dangerous to leave the balancer by accident, so it is only
ever enabled after fixing, it will never be forced off because of
racing.
When hbck is run in fixer mode, it must take an exclusive lock and
disable the balancer, or all havoc will break loose.
If you want to stop hbck from running in parallel, the -exclusive flag
will create the lock file. If you want to force -disableBalancer, that
option is available too. This makes more semantic sense than -noLock and
-noSwitchBalancer, respectively.
> Add -noLock and -noBalanceSwitch options to hbck
> ------------------------------------------------
>
> Key: HBASE-14092
> URL: https://issues.apache.org/jira/browse/HBASE-14092
> Project: HBase
> Issue Type: Bug
> Components: hbck, util
> Affects Versions: 2.0.0, 1.3.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: HBASE-14092-v1.patch, HBASE-14092-v2.patch,
> HBASE-14092.patch
>
>
> HBCK is sometimes used as a way to check the health of the cluster. When
> doing that it's not necessary to turn off the balancer. As such it's not
> needed to lock other runs of hbck out.
> We should add the --no-lock and --no-balancer command line flags.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
