[
https://issues.apache.org/jira/browse/CASSANDRA-17613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576874#comment-17576874
]
David Capwell commented on CASSANDRA-17613:
-------------------------------------------
the 4.0 branch I am +1 with minor comments, [~marcuse] should we block 4.1?
Think we would need to as the 4.0 branch would assume that 4.1.0 would support
this.
> 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: 10m
> 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]
