Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4945D180F5 for ; Thu, 3 Dec 2015 21:38:18 +0000 (UTC) Received: (qmail 8012 invoked by uid 500); 3 Dec 2015 21:38:11 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 7900 invoked by uid 500); 3 Dec 2015 21:38:11 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 7862 invoked by uid 99); 3 Dec 2015 21:38:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Dec 2015 21:38:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0D3822C1F72 for ; Thu, 3 Dec 2015 21:38:11 +0000 (UTC) Date: Thu, 3 Dec 2015 21:38:11 +0000 (UTC) From: "Paulo Motta (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-9294) Streaming errors should log the root cause MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-9294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038644#comment-15038644 ] 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: ||2.1||2.2||3.0||trunk|| |[branch|https://github.com/apache/cassandra/compare/cassandra-2.1...pauloricardomg:2.1-9294-v2]|[branch|https://github.com/apache/cassandra/compare/cassandra-2.2...pauloricardomg:2.2-9294-v2]|[branch|https://github.com/apache/cassandra/compare/cassandra-3.0...pauloricardomg:3.0-9294-v2]|[branch|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:trunk-9294-v2]| |[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-2.1-9294-v2-testall/lastCompletedBuild/testReport/]|[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-2.2-9294-v2-testall/lastCompletedBuild/testReport/]|[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-3.0-9294-v2-testall/lastCompletedBuild/testReport/]|[testall|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-9294-v2-testall/lastCompletedBuild/testReport/]| |[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-2.1-9294-v2-dtest/lastCompletedBuild/testReport/]|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-2.2-9294-v2-dtest/lastCompletedBuild/testReport/]|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-3.0-9294-v2-dtest/lastCompletedBuild/testReport/]|[dtest|http://cassci.datastax.com/view/Dev/view/paulomotta/job/pauloricardomg-trunk-9294-v2-dtest/lastCompletedBuild/testReport/]| [~brandon.williams] mind reviewing this trivial patch? > 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)