You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the ClickHouse Keeper for data replication of multiple RDS databases between two servers. The replication is configured using the ReplicatedReplacingMergeTree engine in ClickHouse. I have set up multiple Altinity Sink Connector jobs to handle data replication from various databases.
However, I am encountering an issue when tables with the same name exist in different databases. For example, the rules table exists in multiple databases, and I receive the following error when running the sink connector jobs:
It appears that the replication path for tables is not distinguishing between databases and is only considering the table name, leading to conflicts when tables with the same name of different databases are being replicated.
Below is the current setup for my two clickhouse-servers:
server 1:
<macros> <cluster>cluster_write</cluster> <shard>1</shard> <replica>replica_1</replica> </macros> <default_replica_path>/clickhouse/tables/{shard}/{database}/{table}</default_replica_path> <default_replica_name>{replica}</default_replica_name>
server 2:
I am using the ClickHouse Keeper for data replication of multiple RDS databases between two servers. The replication is configured using the ReplicatedReplacingMergeTree engine in ClickHouse. I have set up multiple Altinity Sink Connector jobs to handle data replication from various databases.
However, I am encountering an issue when tables with the same name exist in different databases. For example, the rules table exists in multiple databases, and I receive the following error when running the sink connector jobs:
Replica /clickhouse/tables/1/rules/replicas/replica_1 already exists. (REPLICA_ALREADY_EXISTS)
It appears that the replication path for tables is not distinguishing between databases and is only considering the table name, leading to conflicts when tables with the same name of different databases are being replicated.
Below is the current setup for my two clickhouse-servers:
server 1:
<macros> <cluster>cluster_write</cluster> <shard>1</shard> <replica>replica_1</replica> </macros> <default_replica_path>/clickhouse/tables/{shard}/{database}/{table}</default_replica_path> <default_replica_name>{replica}</default_replica_name>
server 2:
<macros> <cluster>cluster_write</cluster> <shard>1</shard> <replica>replica_2</replica> </macros> <default_replica_path>/clickhouse/tables/{shard}/{database}/{table}</default_replica_path> <default_replica_name>{replica}</default_replica_name>
The text was updated successfully, but these errors were encountered: