Skip to content

issue 386 - handle cluster token overlap issue gracefully#387

Draft
msmygit wants to merge 2 commits intomainfrom
feat/handle_cluster_token_overlap_gracefully.md
Draft

issue 386 - handle cluster token overlap issue gracefully#387
msmygit wants to merge 2 commits intomainfrom
feat/handle_cluster_token_overlap_gracefully.md

Conversation

@msmygit
Copy link
Member

@msmygit msmygit commented Sep 8, 2025

What this PR does: Handle cluster token overlap issues more gracefully and educates users on potential fixes and provides clarity

Which issue(s) this PR fixes:
Fixes #386

Checklist:

  • Automated Tests added/updated
  • Documentation added/updated
  • CLA Signed: DataStax CLA

@msmygit msmygit self-assigned this Sep 8, 2025
@msmygit msmygit added the enhancement New feature or request label Sep 8, 2025
@msmygit msmygit force-pushed the feat/handle_cluster_token_overlap_gracefully.md branch 2 times, most recently from 7a29abd to 3c609dd Compare September 8, 2025 16:43
@msmygit msmygit force-pushed the feat/handle_cluster_token_overlap_gracefully.md branch from 3c609dd to e632182 Compare September 10, 2025 14:50

try {
// Execute query to check for token ranges for the specific keyspace
String query = "SELECT start_token, end_token FROM system.size_estimates WHERE keyspace_name = ?";
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will have to evaluate if this is same across different flavors of C* engines, e.g. OSS C*, DSE, HCD, Astra DB, etc.,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handle cluster token overlap issue more gracefully and provide clear failure reasons during migration

1 participant

Comments