[
https://issues.apache.org/jira/browse/CASSANDRA-17613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584644#comment-17584644
]
Marcus Eriksson commented on CASSANDRA-17613:
---------------------------------------------
tests look fine, I'll get this committed once 4.0.6 has been released (so we
can set the correct 4.0 since version (4.0.7-SNAPSHOT) without breaking the
tests)
4.0:
https://app.circleci.com/pipelines/github/krummas/cassandra/810/workflows/d2ee32db-cbeb-4741-a674-ca0b4f9b2a81
4.1:
https://app.circleci.com/pipelines/github/krummas/cassandra/814/workflows/5d10dc0a-0359-4e10-89ef-d4f8f9b2a187
trunk:
https://app.circleci.com/pipelines/github/krummas/cassandra/815/workflows/4f388b44-c478-4682-a17b-52a04f99a163
> Avoid getting hanging repairs due to repair message timeouts
> ------------------------------------------------------------
>
> Key: CASSANDRA-17613
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17613
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 4.0.x, 4.1-beta
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> In 4.0 repair messages can get expired before reaching a replica, this causes
> repairs to hang.
> CASSANDRA-16909 is meant to fix this, but we need a stopgap fix in 4.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
