Support globalOutstandingLimit (#128)

deric · Aug 12, 2019 · 3a16b73 · 3a16b73
1 parent ad24393
commit 3a16b73
Show file tree

Hide file tree

Showing 6 changed files with 114 additions and 85 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,3 +1,8 @@
+## 0.8.7
+- New features:
+  - [Support global outstanding limit](https://github.com/deric/puppet-zookeeper/issues/128) (#128)
+- [Full diff](https://github.com/deric/puppet-zookeeper/compare/v0.8.6...v0.8.7)
+
 ## 0.8.6
 - New features:
   - [Support commands whitelist](https://github.com/deric/puppet-zookeeper/issues/135) (#135)

diff --git a/README.md b/README.md
@@ -164,6 +164,7 @@ After=network-online.target
    - `snap_retain_count` - number of snapshots that will be kept after purging (since ZooKeeper 3.4.0)
    - `min_session_timeout` - the minimum session timeout in milliseconds that the server will allow the client to negotiate. Defaults to 2 times the **tickTime** (since ZooKeeper 3.3.0)
    - `max_session_timeout` - the maximum session timeout in milliseconds that the server will allow the client to negotiate. Defaults to 20 times the **tickTime** (since ZooKeeper 3.3.0)
+   - `global_outstanding_limit` - ZooKeeper will throttle clients so that there is no more than `global_outstanding_limit` outstanding requests in the system.
    - `manage_service` (default: `true`) whether Puppet should ensure running service
    - `manage_service_file` when enabled on RHEL 7.0 a systemd config will be managed
    - `ensure_account` controls whether `zookeeper` user and group will be ensured (set to `false` to disable this feature)