belliottsmith opened a new pull request, #3773:
URL: https://github.com/apache/cassandra/pull/3773
… in a later epoch that is not owned by the replicas
Improve:
- Remove GetMaxConflict; use local MaxConflict collection
Fix:
- Invalidated should retain StoreParticipants so we can update CFK on
journal replay
- loading pruned uninitialised commands via CFK: make sure hasTouched
contains key so that if invalidated we are notified - updateExecuteAtLeast
should always be higher than TxnId - Async CFK callbacks treated pruned
transactions incorrectly - node.withEpoch when ExecuteEphemeralRead in
futureEpoch - Deps.without should be key/range aware - Durably mark
bootstrapBeganAt and safeToReadAt in MaxConflicts - Don't attempt to calculate
local deps when DepsErased in GetLatestDeps (command has durably applied to
this shard) - filter StoreParticipants before invoking shouldCleanup
Thanks for sending a pull request! Here are some tips if you're new here:
* Ensure you have added or run the [appropriate
tests](https://cassandra.apache.org/_/development/testing.html) 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](https://cassandra.apache.org/_/development/index.html)
* If you're making a documentation change, see our [guide to documentation
contribution](https://cassandra.apache.org/_/development/documentation.html)
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](https://issues.apache.org/jira/projects/CASSANDRA/issues/)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
