Skip to content

Conversation

belliottsmith
Copy link
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

ifesdjeen and others added 5 commits September 18, 2025 15:49
To support recovering a node that has lost some of its local transaction log, introduce rebootstrap and unsafe bootstrap modes, where Accord ensures no responses are produced for transactions the node cannot be certain it had not previously answered.

patch by Benedict and Alex Petrov for CASSANDRA-20908
Also Improve:
 - Searchable system_accord_debug.txn

patch by Benedict; reviewed by Aleksey Yeschenko for CASSANDRA-20899
 - Integrate txn_blocked_by deadline and depth filter with execution logic, to ensure we terminate promptly and get a best effort reply
…irtual tables from any node in the cluster

patch by Benedict; reviewed by Alex Petrov for CASSANDRA-20900
 - Introduce pattern tracing, that can intercept failed or new coordinations matching various filters
 - Support additional tracing event collection modes (SAMPLE and RING)

patch by Benedict; reviewed by Alex Petrov for CASSANDRA-20911
@ifesdjeen
Copy link
Contributor

I hope this is not too confusing: as of moment of writing this, Improve Tracing (this) PR contains multiple commits, starting with rebootstrap. To make review simpler to track, I have made a separate PR where only tracing commit is displayed: belliottsmith#8 My (minor) comments are on the PR.

@ifesdjeen ifesdjeen self-requested a review September 26, 2025 09:08
Copy link
Contributor

@ifesdjeen ifesdjeen left a comment

Choose a reason for hiding this comment

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

+1 as long as critical comments in belliottsmith#8 are either addressed or explained (in case my assumptions were wrong).

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.

2 participants