[ https://issues.apache.org/jira/browse/HBASE-11405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141007#comment-14141007 ]
Lars Hofhansl commented on HBASE-11405: --------------------------------------- We can attach backport patches here since neither 0.99.1 nor 2.0.0 are released. > Multiple invocations of hbck in parallel disables balancer permanently > ----------------------------------------------------------------------- > > Key: HBASE-11405 > URL: https://issues.apache.org/jira/browse/HBASE-11405 > Project: HBase > Issue Type: Bug > Components: Balancer, hbck > Affects Versions: 0.99.0 > Reporter: bharath v > Assignee: bharath v > Fix For: 2.0.0, 0.99.1 > > Attachments: 11405-1.0.txt, 11405-v3.txt, 11405-v5.patch, > 11405-v6.patch, 11405v7.patch, HBASE-11405-trunk-rebased.patch, > HBASE-11405-trunk.patch, HBASE-11405-trunk.patch.1, > hbase-11405.rebase.140911.patch > > > This is because of the following piece of code in hbck > {code:borderStyle=solid} > boolean oldBalancer = admin.setBalancerRunning(false, true); > try { > onlineConsistencyRepair(); > } > finally { > admin.setBalancerRunning(oldBalancer, false); > } > {code} > Newer invocations set oldBalancer to false as it was disabled by previous > invocations and this disables balancer permanently unless its manually turned > on by the user. Easy to reproduce, just run hbck 100 times in a loop in 2 > different sessions and you can see that balancer is set to false in the > HMaster logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)