[
https://issues.apache.org/jira/browse/GEODE-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646772#comment-14646772
]
ASF subversion and git services commented on GEODE-124:
-------------------------------------------------------
Commit 1683361bc87368e48d8cfefebf6dbcda932ed90c in incubator-geode's branch
refs/heads/develop from Ashvin Agrawal
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=1683361 ]
GEODE-124: Add min size check and optimize calls
* Member stats are needed for computing member load skew and total data size.
The gathering step is common and need not be executed twice
* If the total transfer size during rebalance is low, then avoid rebalance. This
could happen when a new cluster is created is data is being loaded
> Ability to auto-rebalance data
> ------------------------------
>
> Key: GEODE-124
> URL: https://issues.apache.org/jira/browse/GEODE-124
> Project: Geode
> Issue Type: New Feature
> Affects Versions: 1.0.0-incubating
> Reporter: Ashvin
> Assignee: Ashvin
> Attachments: GEODE-AutomatedRebalancing-150715.pdf
>
>
> Rebalancing relocates data from heavily loaded members to lightly loaded
> members. Currently Geode only supports manual rebalancing by issuing a gfsh
> command or a java function call. In most cases, the decision to rebalance is
> based on the size of the member. As Geode monitors the data size, it can also
> automatically trigger rebalancing. Auto-Rebalancing is expected to prevent
> failures seen in an unbalanced cluster more than with a manual rebalance.
> Latest spec:
> https://cwiki.apache.org/confluence/display/GEODE/Automated+Rebalancing
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
