You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Joshua McKenzie (JIRA)" <ji...@apache.org> on 2015/12/04 17:51:11 UTC
[jira] [Updated] (CASSANDRA-9294) Streaming errors should log the
root cause
[ https://issues.apache.org/jira/browse/CASSANDRA-9294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua McKenzie updated CASSANDRA-9294:
---------------------------------------
Reviewer: Yuki Morishita
> Streaming errors should log the root cause
> ------------------------------------------
>
> Key: CASSANDRA-9294
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9294
> Project: Cassandra
> Issue Type: Improvement
> Components: Streaming and Messaging
> Reporter: Brandon Williams
> Assignee: Paulo Motta
> Fix For: 3.2, 2.1.x, 2.2.x, 3.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)