Skip to content

CASSANDRA-20476 Cluster is unable to recover after shutdown if IPs change - #4980

Open
beobal wants to merge 30 commits into
apache:trunkfrom
beobal:samt/CASSANDRA-20476-trunk
Open

CASSANDRA-20476 Cluster is unable to recover after shutdown if IPs change#4980
beobal wants to merge 30 commits into
apache:trunkfrom
beobal:samt/CASSANDRA-20476-trunk

Conversation

@beobal

@beobal beobal commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Thanks for sending a pull request! Here are some tips if you're new here:

  • Ensure you have added or run the appropriate tests for your PR.
  • Be sure to keep the PR description updated to reflect all changes.
  • Write your PR title to summarize what this PR proposes.
  • If possible, provide a concise example to reproduce the issue for a faster review.
  • Read our contributor guidelines
  • If you're making a documentation change, see our guide to documentation contribution

Commit messages should follow the following format:

<One sentence description, usually Jira title or CHANGES.txt summary>

<Optional lengthier description (context on patch)>

patch by <Authors>; reviewed by <Reviewers> for CASSANDRA-#####

Co-authored-by: Name1 <email1>
Co-authored-by: Name2 <email2>

The Cassandra Jira

beobal and others added 29 commits July 29, 2026 14:58
If two nodes restart with new broadcast addresses concurrently
and one is a CMS member, the non-member may send a TCM_COMMIT_REQ
containing its STARTUP transform to the CMS member's old address.
If this is no longer reachable, the sender should time out quickly
so it can resend to another CMS member, or try to discover the new
CMS address(es).
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.

1 participant