[ https://issues.apache.org/jira/browse/CASSANDRA-20312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955139#comment-17955139 ]
Michael Semb Wever commented on CASSANDRA-20312: ------------------------------------------------ CASSANDRA-18816 is available in 5.0, so we might have missed it, and if it addresses the issue would mean this issue still applies to 4.x > 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.18, 4.1.9, 5.0.4, 5.1 > > > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org