[
https://issues.apache.org/jira/browse/CASSANDRA-20014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Eggleston updated CASSANDRA-20014:
----------------------------------------
Fix Version/s: 4.0.16
Since Version: 4.0
Source Control Link:
https://github.com/apache/cassandra/commit/4f0ad22f122f8233aa99545bc234083690f53ea7
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> 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
> Fix For: 4.0.16
>
> Attachments: 20014_4.0_1_ci_summary.html,
> 20014_4.0_2_ci_summary.html, 20014_4.1_1_ci_summary.html,
> 20014_4.1_2_ci_summary.html, 20014_5.0_1_ci_summary.html,
> 20014_5.0_2_ci_summary.html, 20014_trunk_1_ci_summary.html,
> 20014_trunk_2_ci_summary.html
>
>
> 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]
