Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <17495345.274901296250843886.JavaMail.jira@thor>
Date: Fri, 28 Jan 2011 16:40:43 -0500 (EST)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-2073) Streaming occasionally makes
 gossip back up
In-Reply-To: <1184848.273211296247723428.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams commented on CASSANDRA-2073:
---------------------------------------------

Appears to be the receiver.  I just repro'd it with decom.  Nodes A, B, and C.  Decom B, streams to A and C complete, and afterwards A and C cannot gossip to each other for approximately 40s or so.  B did get the usual exception:

{noformat}
ERROR [Thread-6] 2011-01-28 21:23:08,720 AbstractCassandraDaemon.java (line 119) Fatal exception in thread Thread[Thread-6,5,main]
java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut down
        at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:62)
        at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
        at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:658)
        at org.apache.cassandra.net.MessagingService.receive(MessagingService.java:387)
        at org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:91)
{noformat}

(I had CASSANDRA-2072 applied to avoid other problems) and I don't see any message about streaming completing on it, though A and C show StreamInSessions finishing right before the gossip outage.

> Streaming occasionally makes gossip back up
> -------------------------------------------
>
>                 Key: CASSANDRA-2073
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2073
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Brandon Williams
>            Priority: Minor
>
> Streaming occasionally makes gossip back up, causing nodes to mark each other as down even though the network is ok.  This appears to happen just after streaming has finished.  I noticed this in the course of working on CASSANDRA-2072, so decommission is one way to reproduce.  It seems to happen maybe one of fifteen or twenty tries, so it's fairly rare.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.