Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[xCluster] Same name Inbound and Outbound replication_id should not be allowed #22485

Open
1 task done
gargsans-yb opened this issue May 22, 2024 · 0 comments
Open
1 task done
Assignees
Labels
area/docdb YugabyteDB core features kind/bug This issue is a bug priority/medium Medium priority issue xCluster Label for xCluster related issues/improvements

Comments

@gargsans-yb
Copy link
Contributor

gargsans-yb commented May 22, 2024

Jira Link: DB-11411

Description

Description

Currently Inbound and Outbound replication_id can be same for a cluster.
Example Test Case:

127.0.0.1 (source) -> 127.0.0.2 (destination) (replication_id = test-xcluster1)
127.0.0.2 (source) -> 127.0.0.3 (destination) (replication_id = test-xcluster1)

Inbound and Outbound groups with same name should be blocked.

Issue Type

kind/bug

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.
@gargsans-yb gargsans-yb added area/docdb YugabyteDB core features xCluster Label for xCluster related issues/improvements status/awaiting-triage Issue awaiting triage labels May 22, 2024
@yugabyte-ci yugabyte-ci added kind/bug This issue is a bug priority/medium Medium priority issue and removed status/awaiting-triage Issue awaiting triage labels May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docdb YugabyteDB core features kind/bug This issue is a bug priority/medium Medium priority issue xCluster Label for xCluster related issues/improvements
Projects
None yet
Development

No branches or pull requests

3 participants