Skip to content

docs(plugin_configuration): clarify clusterName uniqueness scope - #41

Open
gabriele-wolfox wants to merge 2 commits into
mainfrom
dev/8999
Open

docs(plugin_configuration): clarify clusterName uniqueness scope#41
gabriele-wolfox wants to merge 2 commits into
mainfrom
dev/8999

Conversation

@gabriele-wolfox

@gabriele-wolfox gabriele-wolfox commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

The clusterName field is the identity key for a cluster's WAL/backup stream on the Klio server it registers with, but this was only documented as an override field without noting its scope.
Two clusters in different namespaces sharing the same clusterName on one server get WAL streaming rejected with a system ID mismatch error, which is safe but previously undocumented.

Fixes #40

The clusterName field is the identity key for a cluster's WAL/backup
stream on the Klio server it registers with, but this was only
documented as an override field without noting its scope. Two
clusters in different namespaces sharing the same clusterName on one
server get WAL streaming rejected with a system ID mismatch error,
which is safe but previously undocumented.

Fixes #40

Signed-off-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com>
Comment thread documentation/web/docs/user/plugin_configuration.md
The uniqueness warning only covered concurrent reuse of clusterName across namespaces. Deleting a cluster and later reusing its clusterName on the same server hits the same system ID mismatch error, since the server has no way to tell the old cluster is gone.

Co-authored-by: Hai He <hai.he@enterprisedb.com>
Signed-off-by: Gabriele Quaresima <gabriele.quaresima@enterprisedb.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document that clusterName must be unique per Klio server, not per namespace

2 participants