We’re trying to setup multi-cluster replication between three self-hosted Temporal clusters and get errors:
Operation failed with internal error. UpdateAckLevel operation encountered concurrent write.
I tracked where it comes from, and it looks like it is emitted from this line. It updates queue_metadata row when returning replication messages via admin API. As there are two clusters asking for replication messages, I assume it tries to increment row field version that is already incremented while serving request from another cluster (query), and hence we get rowsAffected != 1 , i. e. it is 0. Does it mean that replication to two or more clusters does not work? We use server version v1.22.7.