cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9294) Streaming errors should log the root cause
Date Thu, 03 Dec 2015 21:38:11 GMT


Paulo Motta commented on CASSANDRA-9294:

Stream error is already logged if there is an exception during a stream session in the local
node. There are 3 situations, however, where an error is not logged:
* Stream session fails because remote peer left
* Stream session fails because remote peer restarted
* Stream session exception on remote peer

Added patch that logs errors on these situations. Submitted dtests cassci run just in case
the new errors break up existing dtests:

[~brandon.williams] mind reviewing this trivial patch?

> Streaming errors should log the root cause
> ------------------------------------------
>                 Key: CASSANDRA-9294
>                 URL:
>             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,

This message was sent by Atlassian JIRA

View raw message