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

Posted to commits@cassandra.apache.org by "Jose Martinez Poblete (JIRA)" <ji...@apache.org> on 2015/05/04 19:56:08 UTC

[jira] [Commented] (CASSANDRA-9294) Streaming errors should log the root cause

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

Jose Martinez Poblete commented on CASSANDRA-9294:
--------------------------------------------------

It would be very useful to have instead of having to enable TCP logging after the fact

> Streaming errors should log the root cause
> ------------------------------------------
>
>                 Key: CASSANDRA-9294
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9294
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Brandon Williams
>            Assignee: Yuki Morishita
>             Fix For: 2.0.x
>
>
> Currently, when a streaming error occurs all you get is something like:
> {noformat}
> java.util.concurrent.ExecutionException: org.apache.cassandra.streaming.StreamException: Stream failed
> {noformat}
> Instead, we should log the root cause.  Was the connection reset by peer, did it timeout, etc?



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