You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2015/06/04 20:28:38 UTC

[jira] [Updated] (CASSANDRA-9238) Race condition after shutdown gossip message

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

Aleksey Yeschenko updated CASSANDRA-9238:
-----------------------------------------
    Fix Version/s:     (was: 2.1.x)
                   2.2.0 beta 1
                   2.1.6

> Race condition after shutdown gossip message
> --------------------------------------------
>
>                 Key: CASSANDRA-9238
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9238
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sergio Bossa
>            Assignee: Sergio Bossa
>            Priority: Minor
>             Fix For: 2.2.0 beta 1, 2.0.15, 2.1.6
>
>         Attachments: 2.0-CASSANDRA-9238-v2.txt, 2.0-CASSANDRA-9238.txt
>
>
> CASSANDRA-8336 introduced a race condition causing gossip messages to be sent to shutdown nodes even if they have been already marked dead.
> That's because CASSANDRA-8336 changed (among other things) the way the SHUTDOWN gossip message is sent by moving it before the gossip task (the one sending SYN messages), and by putting a few secs wait between the two; this opens a race window by the receiving side between the time the SHUTDOWN message is received, causing the outbound sockets to be closed, and the moment the other side listening socket is actually closed, meaning that any SYN gossip message exchanged in such window will reopen the sockets and never close them again, as the node is already marked dead. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)