Skip to content

Conversation

@nookyo
Copy link
Collaborator

@nookyo nookyo commented Jun 17, 2025

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

belliottsmith and others added 30 commits April 17, 2025 11:59
ninja: fix NPE
disable ephemeral reads
don't load range commands that are redundant, and load least possible
use MISC verb handler for maintenance tasks
…hutdown until after MS.

Wake up segment prepared after shutting down allocator, as no new segments will ever be allocated.

Shut down flusher slightly differently: we do not signal from fsync complete, since all blocks should have been fsynced by then, but we will add invariant check to notice runaway threads.

Wait for quiescense

Truncate blocking

Wait for scheduler shutdown before shutting down command store

Shut down accord after shutting down messaging

Truncate caches before replay
split JournalKey in journal table so we can index it
reorder journal fields so we can easily index on route (when present)
use Message.expiresAtNanos for callback expiration
do not notify slow for range barriers

Accord: Do not contact faulty replicas, and promptly report slow replies for preaccept/read. Do not wait for stale or left nodes for durability.
…edup RoutingKey tableId; avoid calculating rejectsFastPath in more cases; delay retry of fetchMajorityDeps; fix SetShardDurable marking shards durable
… to ReconfigureAccordFastPath so the TCM logs/table gives the debug info needed
…low replies for preaccept/read. Do not wait for stale or left nodes for durability.
update durability scheduling and majority deps fetching
do not deserialize deps in CommandsForRangesLoader unless required

AccordJournalPurger should use shouldCleanupPartial

load historical transactions when loading topology
Patch by Ariel Weisberg; Reviewed by David Capwell for CASSANDRA-19955

Non-serial single partition reads on Accord

Patch by Ariel Weisberg; Reviewed by Benedict Elliott Smith for CASSANDRA-19951
Fix NPE in MockJournal on null onFlush
Fix SavedCommandTest.
After the serialization change that serializes "changed" before "is null", null flag can no be written.
… to be empty, should also populate there as well

patch by David Capwell; reviewed by Benedict Elliott Smith for CASSANDRA-20017
patch by David Capwell; reviewed by Ariel Weisberg for CASSANDRA-20020
…fter reaching rf=3

patch by David Capwell; reviewed by Alex Petrov for CASSANDRA-19975
Patch by Alex Petrov; reviewed by Ariel Weisberg for CASSANDRA-20032

Accord Deps tests have incorrect range semantics

patch by David Capwell; reviewed by Ariel Weisberg for CASSANDRA-20029
For correctness, the dependencies we adopt on joining a new topology must exclude the possibility of respondents accepting additional transactions with a lower TxnId, so proxying on the existing `ExclusiveSyncPoint` mechanisms is logical for the time-being. This patch removes the `FetchMajorityDeps` logic in favour of simply waiting for a suitable `ExclusiveSyncPoint` to be proposed.

patch by Benedict, reviewed by Alex Petrov for CASSANDRA-20056
…pologyMixupTestBase

patch by David Capwell; reviewed by Alex Petrov, David Capwell for CASSANDRA-20054
Patch by Ariel Weisberg; Reviewed by David Capwell for CASSANDRA-20060
…locks and performance issues

patch by David Capwell; reviewed by Benedict Elliott Smith for CASSANDRA-20065
Patch by Ariel Weisberg; Reviewed by Benedict Elliott Smith for CASSANDRA-19436
patch by Aleksey Yeschenko; reviewed by Benedict Elliott Smith and David
Capwell for CASSANDRA-20062
Patch by Ariel Weisberg; Reviewed by Benedict Elliott Smith for CASSANDRA-19437
patch by Aleksey Yeschenko; reviewed by Benedict Elliott Smith for
CASSANDRA-20062
driftx and others added 30 commits May 28, 2025 17:29
Patch by Venkata Harikrishna Nukala; reviewed by Marcus Eriksson and Sam
Tunnicliffe for CASSANDRA-18509
 - cfk pruning+prebootstrap=invalid future dependency
 - exclude retired ranges when filtering RX stillTouches
 - propagate uses incorrect lowEpoch when fetch finds additional owned/touched ranges
 - node.withEpoch should callback with TopologyRetiredException, not throw
 - Recovery can race with durable-applied pruning; must not send durable unless latest ballot on apply
 - removeRedundantDependencies was not slicing pre-bootstrap range calculation to participating ranges
 - NPE in TopologyManager.atLeast caused by referencing an epoch that has been GC'd
 - use journal durableBeforePersister in burn test, not NOOP_PERSISTER
 - ServerUtils.cleanupDirectory use tryDeleteRecursive
 - FsyncRunnable shutdown
 - fix NPE in AccordJournalBurnTest

patch by Benedict; reviewed by Alex Petrov for CASSANDRA-20688
…s) to 4.1 and 5.0

patch by Ariel Weisberg; reviewed by Benedict Elliott Smith for CASSANDRA-20585
Patch by Ariel Weisberg and Yuqi Yan; Reviewed by Marcus Eriksson for CASSANDRA-20513

Co-authored-by: Yuqi Yan <yukei0509@gmail.com>
patch by Dmitry Konstantinov; reviewed by Michael Semb Wever, Stefan Miklosovic for CASSANDRA-20681
patch by Ling Mao; reviewed by Stefan Miklosovic, Maxim Muzafarov for CASSANDRA-20499

Co-authored-by: Stefan Miklosovic <smiklosovic@apache.org>
…g BtiFormat

Patch by marcuse; reviewed by Mick Semb Wever for CASSANDRA-18119
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.