[
https://issues.apache.org/jira/browse/CASSANDRA-16721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405460#comment-17405460
]
Caleb Rackliffe edited comment on CASSANDRA-16721 at 8/26/21, 11:07 PM:
------------------------------------------------------------------------
||Branch||Circle CI||Apache CI||
|[4.0|https://github.com/apache/cassandra/pull/1160]|[J8 and
J11|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-16721-4.0]|[1066|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1066/]|
|[trunk|https://github.com/apache/cassandra/pull/1171]|[J8 and
J11|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-16721-trunk]|[1074|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1074/]|
UPDATE: The changes in CASSANDRA-16850 introduced a few minor conflicts for the
trunk patch, and I've addressed those
[here|https://github.com/apache/cassandra/pull/1171]. Tests are running again,
and in the meantime, I'm likely going to make a few of those changes to the 4.0
patch as well just to keep things consistent.
was (Author: maedhroz):
||Branch||Circle CI||Apache CI||
|[4.0|https://github.com/apache/cassandra/pull/1160]|[J8 and
J11|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-16721-4.0]|[1066|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1066/]|
|[trunk|https://github.com/apache/cassandra/pull/1171]|[J8 and
J11|https://app.circleci.com/pipelines/github/maedhroz/cassandra?branch=CASSANDRA-16721-trunk]|[1067|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1067/]|
> Repaired data tracking on a read coordinator is susceptible to races between
> local and remote requests
> ------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16721
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16721
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
> Reporter: Sam Tunnicliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 4.0.x, 4.x
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> At read time on a coordinator which is also a replica, the local and remote
> reads can race such that the remote responses are received while the local
> read is executing. If the remote responses are mismatching, triggering a
> {{DigestMismatchException}} and subsequent round of full data reads and read
> repair, the local runnable may find the {{isTrackingRepairedStatus}} flag
> flipped mid-execution. If this happens after a certain point in execution,
> it would mean
> that the RepairedDataInfo instance in use is the singleton null object
> {{RepairedDataInfo.NULL_REPAIRED_DATA_INFO}}. If this happens, it can lead to
> an NPE when calling {{RepairedDataInfo::extend}} when the local results are
> iterated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
