You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2011/06/20 14:35:47 UTC

[jira] [Updated] (CASSANDRA-2797) Repair hangs if a neighbor has nothing to send

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

Sylvain Lebresne updated CASSANDRA-2797:
----------------------------------------

    Attachment: 0001-Always-initiate-streaming-transfer-to-notify-remote-.patch

Apparently the code was already wired to handle initiating a session with nothing to transfer, but a if prevented that code path. Patch attached against 0.7.

> Repair hangs if a neighbor has nothing to send 
> -----------------------------------------------
>
>                 Key: CASSANDRA-2797
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2797
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.6
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>              Labels: repair, streaming
>             Fix For: 0.7.7, 0.8.2
>
>         Attachments: 0001-Always-initiate-streaming-transfer-to-notify-remote-.patch
>
>
> This is actually a streaming problem. If a StreamOutSession has nothing to transfer (i.e, no sstables have the requested ranges), it will not even initiate the transfer and simply close the session right away. The problem is that if the session was initiated by a remote end (through a StreamRequestMessage), the remote end will never be notified and never run his callback.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira