[jira] [Updated] (HBASE-14201) hbck should not take a lock unless fixing errors
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Law updated HBASE-14201: -- Release Note: HBCK no longer takes a lock until there are changes to the cluster being made. The old behavior can be achieved by passing the -exclusive flag. was: HBCK no longer takes a lock until there are changes to the cluster being made. The old behavior can be achieved by passing the exclusive flag. > 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 >Assignee: Simon Law > Fix For: 2.0.0, 1.2.0 > > Attachments: HBASE-14201-v0.patch, HBASE-14201-v1.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. > This task is related to HBASE-14092. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14201) hbck should not take a lock unless fixing errors
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-14201: -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: (was: 1.3.0) 1.2.0 Release Note: HBCK no longer takes a lock until there are changes to the cluster being made. The old behavior can be achieved by passing the exclusive flag. Status: Resolved (was: Patch Available) > 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 >Assignee: Simon Law > Fix For: 2.0.0, 1.2.0 > > Attachments: HBASE-14201-v0.patch, HBASE-14201-v1.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. > This task is related to HBASE-14092. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14201) hbck should not take a lock unless fixing errors
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Law updated HBASE-14201: -- Attachment: HBASE-14201-v1.patch Revised patch with fixed tests. > 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 >Assignee: Simon Law > Fix For: 2.0.0, 1.3.0 > > Attachments: HBASE-14201-v0.patch, HBASE-14201-v1.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. > This task is related to HBASE-14092. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14201) hbck should not take a lock unless fixing errors
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-14201: -- Assignee: Simon Law Fix Version/s: (was: 1.2.0) Status: Patch Available (was: Open) > 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 >Assignee: Simon Law > Fix For: 2.0.0, 1.3.0 > > Attachments: HBASE-14201-v0.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. > This task is related to HBASE-14092. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14201) hbck should not take a lock unless fixing errors
[ https://issues.apache.org/jira/browse/HBASE-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Law updated HBASE-14201: -- Attachment: HBASE-14201-v0.patch > 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 > > Attachments: HBASE-14201-v0.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. > This task is related to HBASE-14092. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
