Skip to content

[docs] Complete ZooKeeper client configuration documentation #4337

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hanliu0830 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[docs] Complete ZooKeeper client configuration documentation #4337

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion website/docs/maintenance/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,8 @@ The logging-related environment options (`env.log.dir`, `env.log.level`, `env.lo
| zookeeper.client.tolerate-suspended-connections | Boolean | false | Defines whether a suspended ZooKeeper connection will be treated as an error that causes the leader information to be invalidated or not. In case you set this option to %s, Fluss will wait until a ZooKeeper connection is marked as lost before it revokes the leadership of components. This has the effect that Fluss is more resilient against temporary connection instabilities at the cost of running more likely into timing issues with ZooKeeper. |
| zookeeper.client.ensemble-tracker | Boolean | true | Defines whether Curator should enable ensemble tracker. This can be useful in certain scenarios in which CuratorFramework is accessing to ZK clusters via load balancer or Virtual IPs. Default Curator EnsembleTracking logic watches `CuratorEventType.GET_CONFIG` events and changes ZooKeeper connection string. It is not desired behaviour when ZooKeeper is running under the Virtual IPs. Under certain configurations EnsembleTracking can lead to setting of ZooKeeper connection string with unresolvable hostnames. |
| zookeeper.client.config-path | String | (None) | The file path from which the ZooKeeper client reads its configuration. This allows each ZooKeeper client instance to load its own configuration file, instead of relying on shared JVM-level environment settings. This enables fine-grained control over ZooKeeper client behavior. |
| zookeeper.client.max-inflight-requests | String | 100 | The maximum number of unacknowledged requests the client will send to ZooKeeper before blocking. |
| zookeeper.client.max-inflight-requests | Integer | 100 | The maximum number of unacknowledged requests the client will send to ZooKeeper before blocking. |
| zookeeper.client.max-buffer-size | Integer | 104857600 | The maximum buffer size (in bytes) for the ZooKeeper client. The default is 100 MiB. This sets the client's `jute.maxbuffer` property and overrides the value in `zookeeper.client.config-path`, if configured. The ZooKeeper server's `jute.maxbuffer` limit must be configured separately. |

## Netty

Expand Down