Skip to content

Changes to clickhouse-keeper.md: add embedded keeper section #177

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

Merged
SaltTan merged 3 commits into from
Mar 31, 2026
Merged

Changes to clickhouse-keeper.md: add embedded keeper section #177

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d93628c
Changes to clickhouse-keeper.md: add embedded keeper section
realyota Mar 31, 2026
81d4afa
Changes to clickhouse-keeper.md: add embedded keeper section
realyota Mar 31, 2026
02a1cf5
Merge branch 'mbak_kb_changes' of github.com:realyota/altinityknowled…
realyota Mar 31, 2026
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
6 changes: 4 additions & 2 deletions ...en/altinity-kb-setup-and-maintenance/altinity-kb-zookeeper/clickhouse-keeper.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,12 +72,14 @@ Increasing the number of nodes offers no significant advantages (unless you need

In clickhouse-keeper-client, paths are now parsed more strictly and must be passed as string literals. In practice, this means using single quotes around paths—for example, `ls '/'` instead of `ls /`, and `get '/clickhouse/path'` instead of `get /clickhouse/path`.

## Embedded Keeper

To use the embedded ClickHouse Keeper, add the `<keeper_server>` section to the ClickHouse server configuration. In this setup, a separate client-side `<keeper>` section is not required. If your ClickHouse servers use an external ClickHouse Keeper or ZooKeeper ensemble instead, see the section below.

## Example of a simple cluster

The Keeper ensemble size must be odd because it requires a majority (50% + 1 nodes) to form a quorum. A 2-node Keeper setup will lose quorum after a single node failure, so the recommended number of Keeper replicas is 3.

On `hostname1` and `hostname2` below, ClickHouse can use the embedded Keeper cluster from `<keeper_server>`, so a separate client-side `<keeper>` section is not required. If your ClickHouse servers connect to an external Keeper or ZooKeeper ensemble, see [ClickHouse config for Keeper].

### hostname1

```xml
Expand Down
Loading