[
https://issues.apache.org/jira/browse/GEODE-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313950#comment-16313950
]
ASF GitHub Bot commented on GEODE-4148:
---------------------------------------
bschuchardt opened a new pull request #1241: GEODE-4148 Locator threshold
before rebalancing clients
URL: https://github.com/apache/geode/pull/1241
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.
@upthewaterspout @PivotalSarge @WireBaron @galen-pivotal
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced in
the commit message?
- [ ] Has your PR been rebased against the latest commit within the target
branch (typically `develop`)?
- [ ] Is your initial contribution a single, squashed commit?
- [ ] Does `gradlew build` run cleanly?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and
submit an update to your PR as soon as possible. If you need help, please
send an
email to [email protected].
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
