hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Law (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-14201) hbck should not take a lock unless fixing errors
Date Mon, 10 Aug 2015 18:16:45 GMT
Simon Law created HBASE-14201:

             Summary: hbck should not take a lock unless fixing errors
                 Key: HBASE-14201
                 URL: https://issues.apache.org/jira/browse/HBASE-14201
             Project: HBase
          Issue Type: Bug
          Components: hbck, util
    Affects Versions: 2.0.0, 1.3.0
            Reporter: Simon Law
             Fix For: 2.0.0, 1.2.0, 1.3.0

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

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.

This task is related to HBASE-14092.

This message was sent by Atlassian JIRA

View raw message