Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-21324 [balancer] Gives up too soon when lots of regions
  3. HBASE-21338

[balancer] If balancer is an ill-fit for cluster size, it gives little indication

    XMLWordPrintableJSON

    Details

    • Hadoop Flags:
      Reviewed
    • Release Note:
      Hide
      The description claims the balancer not dynamically configurable but this is an error; it is http://hbase.apache.org/book.html#dyn_config

      Also, if balancer is seen to be cutting out too soon, try setting "hbase.master.balancer.stochastic.runMaxSteps" to true.

      Adds cleaner logging around balancer start.
      Show
      The description claims the balancer not dynamically configurable but this is an error; it is http://hbase.apache.org/book.html#dyn_config Also, if balancer is seen to be cutting out too soon, try setting "hbase.master.balancer.stochastic.runMaxSteps" to true. Adds cleaner logging around balancer start.

      Description

      See parent issue. Running balancer on a cluster where the max steps was way inadequate, the balancer gave little to no indication that it was ill-configured. In fact, it only logged its starting and then that there was nothing to do though the cluster was obviously out-of-whack.

      Ideally the balancer would complain when say the maxSteps limit is a small fraction of what the cluster's calculated max steps are, or it would notice that the balancer is making little progress on an imbalanced cluster and shout. Can we set balancer configs w/o having to restart Master?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                xucang Xu Cang
                Reporter:
                stack Michael Stack
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: