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

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052018#comment-13052018 ] 

Jonathan Ellis commented on CASSANDRA-2797:
-------------------------------------------

I thought transferSSTables is supposed to be only called for locally-initiated transfers, and transferRangesForRequest is for ones initiated remotely.  (Confusing, I know.  This got cleaned up in 0.8.)

> 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