[
https://issues.apache.org/jira/browse/HBASE-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009762#comment-13009762
]
Jean-Daniel Cryans commented on HBASE-3681:
-------------------------------------------
I think there's a small misunderstanding of what the intention of this jira is.
The Balancer should only run if any of the servers are outside of the
sloppiness envelope, it's not on a per region server basis else we would just
be delaying the problem. So, this patch really only needs to add a check before
everything else to see where each region server is with regards to the slop
factor, then make the decision of doing the balance to even out everything.
Also I think the slop should be configured in AssignmentManager, since HMaster
in your patch is really just passing it down.
> Check the sloppiness of the region load before balancing
> --------------------------------------------------------
>
> Key: HBASE-3681
> URL: https://issues.apache.org/jira/browse/HBASE-3681
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.1
> Reporter: Jean-Daniel Cryans
> Assignee: Ted Yu
> Fix For: 0.92.0
>
> Attachments: hbase-3681.txt
>
>
> Per our discussion at the hackathon today, it seems that it would be more
> helpful to add a sloppiness check before doing the normal balancing.
> The current situation is that the balancer always tries to get the region
> load even, meaning that there can be some very frequent regions movement.
> Setting the balancer to run less often (like every 4 hours) isn't much better
> since the load could get out of whack easily.
> This is why running the normal balancer frequently, but first checking for
> some sloppiness in the region load across the RS, seems like a more viable
> option.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
