[
https://issues.apache.org/jira/browse/GEODE-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316800#comment-16316800
]
ASF subversion and git services commented on GEODE-4148:
--------------------------------------------------------
Commit ad74d980604291533c85929a854b3003f379df74 in geode's branch
refs/heads/develop from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ad74d98 ]
GEODE-4148 Locator threshold before rebalancing clients
The server location service is now less aggressive in moving clients
from the most loaded server to the least loaded server. It will wait
until the load difference is 10 times the load-per-connection value,
which defaults to 1. Once this threshold is reached clients will be
moved until balance has been restored.
The threshold can be changed from 10 to some other floating point value
with the system property
gemfire.locator-load-imbalance-threshold
when starting locators. The setting is not needed in clients or
servers.
This closes #1241
> Locator threshold before rebalancing clients
> --------------------------------------------
>
> Key: GEODE-4148
> URL: https://issues.apache.org/jira/browse/GEODE-4148
> Project: Geode
> Issue Type: Improvement
> Components: client/server, locator
> Reporter: Galen O'Sullivan
>
> Clients periodically send ClientReplacementRequests to the locator to
> rebalance the number of client connections across the cluster. When multiple
> clients are getting rebalanced, the lack of any buffering can cause clients
> to move between servers without changing the loading. For example, if there
> are an odd number of clients on an even number of servers, the locator may
> ping-pong clients between the server that has one more client than the others.
> The locator should wait until some threshold to move clients, to avoid
> ping-ponging and unnecessary connection churn.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
