cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-9294) Streaming errors should log the root cause
Date Mon, 04 May 2015 16:51:06 GMT

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

Brandon Williams updated CASSANDRA-9294:
----------------------------------------
    Description: 
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?

  was:
Currently, when a streaming errors 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?


> 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)

Mime
View raw message