[
https://issues.apache.org/jira/browse/CASSANDRA-20312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925602#comment-17925602
]
Michael Semb Wever commented on CASSANDRA-20312:
------------------------------------------------
+1
As said, the update timestamp is only updated from state changes, so we’re only
checking the amount of time since repair phase starts. The fix changes this to
the amount of time since _any_ activity. This has been confirmed with one user
in production to fix the situation of repairs (consistently) prematurely timing
out.
> Long running repairs autofail prematurely
> -----------------------------------------
>
> Key: CASSANDRA-20312
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20312
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: Berenguer Blasi
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> Repairs will autofail after a long period of inactivity but very long-running
> repairs may be incorrectly auto failed. Capture status pings as liveness info.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
