GitHub user mprimi opened a pull request:
https://github.com/apache/zookeeper/pull/215
Four-letter words to voluntarily shed client connections
Introduce 3 new 4-letter commands:
- shed: close all client connections
- sh25: close approximatively 1/4 of client connections
- sh50: close approximatively half of client connections
In clusters with large number of clients, a rolling bounce (or multiple)
can lead to a situation of severe connection imbalance.
In these situations, restarting clients is the only solution to rebalance
the load among servers.
This change introduces server admin command that voluntarily close client
connections.
Clients should be able to migrate transparently to another server, just
like in case of actual disconnection or server crash.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mprimi/zookeeper ZOOKEEPER-2748
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/215.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #215
----
commit f059259cce574803ccca6ee39d0d21ea01eaabc0
Author: Marco Primi <[email protected]>
Date: 2017-03-01T22:19:47Z
Four-letter words to voluntarily shed client connections
Introduce 3 new 4-letter commands:
- shed: close all client connections
- sh25: close approximatively 1/4 of client connections
- sh50: close approximatively half of client connections
In clusters with large number of clients, a rolling bounce (or multiple)
can lead to a situation of severe connection imbalance.
In these situations, restarting clients is the only solution to rebalance
the load among servers.
This change introduces server admin command that voluntarily close client
connections.
Clients should be able to migrate transparently to another server, just
like in case of actual disconnection or server crash.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
