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

Marcus Eriksson updated CASSANDRA-17168:
----------------------------------------
          Fix Version/s: 4.0.2
                         4.1
                             (was: 4.x)
                             (was: 4.0.x)
          Since Version: 4.0
    Source Control Link: 
https://github.com/apache/cassandra/commit/98e798f567368f826fc3a57ddb6cdc464e741fe3
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

> Don't block gossip when clearing snapshots for failing repairs
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-17168
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17168
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Consistency/Repair
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>            Priority: Normal
>             Fix For: 4.0.2, 4.1
>
>
> We clear snapshots in the GossipTasks thread when a repair session fails due 
> to a replica shutting down. If there are many tables/repair sessions ongoing 
> this can take a long time. With enough tables being repaired at the same time 
> even checking if the snapshots exists can take long enough to mark nodes down.
> We should clear snapshots in a separate thread and add a flag to tell us 
> whether this repair session can have snapshots to avoid checking if the 
> directory exists.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to