You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2014/12/12 15:53:14 UTC

[jira] [Commented] (CASSANDRA-8472) Streams hang in repair

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

Yuki Morishita commented on CASSANDRA-8472:
-------------------------------------------

Do you set streaming_socket_timeout_in_ms in cassandra.yaml?
Default is 0, which means no timeout.

We may want to pick different default value.

> Streams hang in repair
> ----------------------
>
>                 Key: CASSANDRA-8472
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8472
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jimmy Mårdell
>         Attachments: errlogs
>
>
> In general streaming is working much better in 2.0.x than before, but we still get occasional hanging stream sessions.
> One of the nodes, the "follower", throws IOException: Broken pipe, causing all streams to fail with the "initiator" node. But the initiator node still thinks its sending and receiving files from the follower, causing the streaming to hang forever.
> Relevant lines from the logs of the "follower" attached. There's nothing relevant in the logs on the initiator node. There are no indications of retry attempts.



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