Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 27 Mar 2015 17:14:53 +0000 (UTC)
From: "Philip Thompson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12761360.1418394528000.51650.1427476493264@Atlassian.JIRA>
In-Reply-To: <JIRA.12761360.1418394528000@Atlassian.JIRA>
References: <JIRA.12761360.1418394528000@Atlassian.JIRA>
 <JIRA.12761360.1418394528587@arcas>
Subject: [jira] [Updated] (CASSANDRA-8472) Streams hang in repair
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CASSANDRA-8472?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Philip Thompson updated CASSANDRA-8472:
---------------------------------------
    Fix Version/s: 2.0.14

> Streams hang in repair
> ----------------------
>
>                 Key: CASSANDRA-8472
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8472
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jimmy M=C3=A5rdell
>             Fix For: 2.0.14
>
>         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, causin=
g all streams to fail with the "initiator" node. But the initiator node sti=
ll thinks its sending and receiving files from the follower, causing the st=
reaming 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 ret=
ry attempts.


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