clickhouse-keeper cluster not working

TL;DR

Issue ClickHouse/clickhouse#56392 (closed, 24 comments): Describe what's wrong I setup clickhouse cluster on three nodes and setup clickhouse-keeper on the same nodes according to the official documents on three virtual machines. the version is : > ClickHouse server version 23.10.1.1976 (official build) > ClickHouse server version 23.10.1.1976 (official build) what works not as it is supposed to. the result of SELECT * FROM system.zookeeper WHERE path IN ('/', '/clickhouse'); is: > 2023.11.06 15:54:29.902052 [ 4478 ] {} [Error] virtual bool DB::DDLWorker::initializeMainThread(): Code: 999.

When to use

You are seeing this: Coordination::Exception: All connection tries fail 2. Use this skill when you run into "clickhouse-keeper cluster not working".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 23.10.1.1976, 2023.11.06. If you are on something much newer or older, the details may have shifted.

Steps

1. Issue ClickHouse/clickhouse#56392 (closed, 24 comments): Describe what's wrong I setup clickhouse cluster on three nodes and setup clickhouse-keeper on the same nodes according to the official documents on three virtual machines. the version is : > ClickHouse server version 23.10.1.1976 (official build) > ClickHouse server version 23.10.1.1976 (official build) what works not as it is supposed to. the result of SELECT * FROM system.zookeeper WHERE path IN ('/', '/clickhouse'); is: > 2023.11.06 15:54:29.902052 [ 4478 ] {} [Error] virtual bool DB::DDLWorker::initializeMainThread(): Code: 999. Coordination::Exception: All connection tries fail

1. If ClickHouse and standalone Keeper run on the same machine, keep their configs in separate directories. The server will start an embedded Keeper using the standalone Keeper's config when both configs live in the same folder, and the cluster breaks. Put the standalone Keeper config in its own directory away from the server's config.xml so the server never picks it up.