[
https://issues.apache.org/jira/browse/CASSANDRA-19495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831667#comment-17831667
]
Stefan Miklosovic commented on CASSANDRA-19495:
-----------------------------------------------
5.0 branch looks good at least for jvm repeats and dtests, I am going to run
j17 pre-commit at least and if we are all good with the verification I will
build it all during Easter.
[CASSANDRA-19495|https://github.com/instaclustr/cassandra/tree/CASSANDRA-19495]
{noformat}
java17_pre-commit_tests
java17_separate_tests
✓ j17_build 4m 5s
✓ j17_dtests 33m 50s
✓ j17_jvm_dtests_repeat 44m 3s
java11_pre-commit_tests
java11_separate_tests
{noformat}
[java17_pre-commit_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/4091/workflows/d007ae15-0538-4f24-a520-ddc3b98677bc]
[java17_separate_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/4091/workflows/083e5d3e-3cea-4980-92d8-1601491fa261]
[java11_pre-commit_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/4091/workflows/d42a7ca7-9cd9-4d6d-a3ac-59c4eab7b848]
[java11_separate_tests|https://app.circleci.com/pipelines/github/instaclustr/cassandra/4091/workflows/4b54b873-5e6b-4a55-baa8-d5937810d206]
> Hints not stored after node goes down for the second time
> ---------------------------------------------------------
>
> Key: CASSANDRA-19495
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19495
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Hints
> Reporter: Paul Chandler
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.1.x, 5.0-rc, 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I have a scenario where a node goes down, hints are recorded on the second
> node and replayed, as expected. If the first node goes down for a second time
> and time span between the first time it stopped and the second time it
> stopped is more than the max_hint_window then the hint is not recorded, no
> hint file is created, and the mutation never arrives at the node after it
> comes up again.
> I have debugged this and it appears to due to the way hint window is
> persisted after https://issues.apache.org/jira/browse/CASSANDRA-14309
> The code here:
> [https://github.com/apache/cassandra/blame/cassandra-4.1/src/java/org/apache/cassandra/service/StorageProxy.java#L2402]
> uses the time stored in the HintsBuffer.earliestHintByHost map. This map is
> based on the UUID of the host, but this does not seem to be cleared when the
> node is back up, and I think this is what is causing the problem.
>
> This is in cassandra 4.1.5
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
