-
Notifications
You must be signed in to change notification settings - Fork 2k
Open
Labels
bugSomething isn't workingSomething isn't workinginstallIssues with installing SigNozIssues with installing SigNoz
Description
Bug description
When deploying SigNoz with a 3-node ClickHouse HA cluster using docker-compose.ha.yaml, the schema migrator fails with replica conflicts. All three ClickHouse nodes attempt to use the same default replica name, causing ZooKeeper to reject subsequent replica registrations.
Error observed:
Replica /clickhouse/tables/.../replicas/example01-01-1 already exists. (REPLICA_ALREADY_EXISTS)
Expected behavior
Each ClickHouse node should have a unique replica name, allowing successful creation of ReplicatedMergeTree tables across the cluster without conflicts.
How to reproduce
- Clone SigNoz repository:
git clone https://github.com/SigNoz/signoz.git - Navigate to deploy/docker:
cd signoz/deploy/docker - Use HA compose:
cp docker-compose.ha.yaml docker-compose.yaml - Deploy:
docker compose up -d - Observe migrator logs:
docker logs signoz-telemetrystore-migrator
Expected: Migrations complete successfully
Actual: Migrator fails with REPLICA_ALREADY_EXISTS error
Version information
- SigNoz version: v0.113.0 (latest main)
- Your OS and version: Ubuntu 22.04
- Your CPU Architecture: x86_64 (Intel/AMD)
Additional context
The fix requires adding unique macros.replica configuration for each ClickHouse node:
macros-1.xmlβ<replica>replica_1</replica>macros-2.xmlβ<replica>replica_2</replica>macros-3.xmlβ<replica>replica_3</replica>
Thank you for your bug report β we love squashing them!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workinginstallIssues with installing SigNozIssues with installing SigNoz