[
https://issues.apache.org/jira/browse/CASSANDRA-20014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17907512#comment-17907512
]
Matt Byrd commented on CASSANDRA-20014:
---------------------------------------
Here are the related branches for 4.0/4.1/5.0:
https://github.com/Jollyplum/cassandra/tree/CASSANDRA-20014-4.0
https://github.com/Jollyplum/cassandra/tree/CASSANDRA-20014-4.1
https://github.com/Jollyplum/cassandra/tree/CASSANDRA-20014-5.0
I'm also attaching 2 runs of CI for each branch.
This generally shows where a test that's flaky and fails in one run succeeds in
the other. (skimming a lot of them also seem to fail sporadically on runs I've
done without the patch)
For a few of the Hint related tests that failed, I tried running them locally
to repro the failure and couldn't.
I kept those ci runs in as they had the fewest other unrelated failures, to in
turn keep the intersection of failures between two runs of a branch lower for
manual inspection.
Let me know what you think.
Thanks
> Discard hints based on write time, not timeout time
> ---------------------------------------------------
>
> Key: CASSANDRA-20014
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20014
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Consistency/Hints
> Reporter: Blake Eggleston
> Assignee: Matt Byrd
> Priority: Normal
>
> Hints are created after a write timeout are created with the timeout time as
> the hint creation time. In the case of slow hint delivery, this can create a
> window of time where a write is applied after gcgs would have elapsed for
> tombstones written after the original write, and the tombstone has been
> purged, causing data resurrection. We should use the time the client request
> thread started working on the request as the hint creation time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
