Skip to content

Commit a9b320b

Browse files
realyotaSaltTan
andauthored
Update content/en/altinity-kb-setup-and-maintenance/altinity-kb-zookeeper/clickhouse-keeper.md
Co-authored-by: SaltTan <20357526+SaltTan@users.noreply.github.com>
1 parent 18908c4 commit a9b320b

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

content/en/altinity-kb-setup-and-maintenance/altinity-kb-zookeeper/clickhouse-keeper.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ See https://kb.altinity.com/altinity-kb-setup-and-maintenance/altinity-kb-zookee
6464

6565
The main issue with a larger Keeper ensemble is that it takes more time to re-elect a leader, and commits take longer, which can slow down insertions and DDL queries.
6666

67-
It should be fine, but we can't recommend running more than that number of zookeeper nodes (except observers).
67+
It should be fine, but we don’t recommend running more than three Keeper nodes (excluding observers).
6868

6969
Increasing the number of nodes offers no significant advantages (unless you need to tolerate the simultaneous failure of two Keeper nodes). In terms of performance, it doesn’t perform better—and may even perform worse—and it consumes additional resources (ZooKeeper requires fast, dedicated disks to perform well, as well as some RAM and CPU).
7070

0 commit comments

Comments
 (0)