[
https://issues.apache.org/jira/browse/HBASE-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-14092:
----------------------------------
Attachment: HBASE-14092-v1.patch
It's not really possible to tell if the user wants to not turn the balancer
off. If the balancer is on there's a possibility that hbck will report
inconsistent even though things are just fine. So not locking is all about how
ok the user is with that chance.
If this command is being run in the background for alerting and flakey alerts
are filtered then they are ok.
If they are running this command to see if action is needed then they probably
aren't ok with a flakey result.
> 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.3.0
>
> Attachments: HBASE-14092-v1.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)
