[ 
https://issues.apache.org/jira/browse/CASSANDRA-17613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marcus Eriksson updated CASSANDRA-17613:
----------------------------------------
          Fix Version/s: 4.0.7
                             (was: 4.0.x)
          Since Version: 4.0-alpha1
    Source Control Link: 
https://github.com/apache/cassandra/commit/5beab63b5550efb5e31e5005f90649661a9fe595
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

and committed, thanks!

> 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.7, 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]

Reply via email to