Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 4 Nov 2014 14:26:34 +0000 (UTC)
From: "Oleg Poleshuk (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12752436.1415025713000.408775.1415111194512@Atlassian.JIRA>
In-Reply-To: <JIRA.12752436.1415025713000@Atlassian.JIRA>
References: <JIRA.12752436.1415025713000@Atlassian.JIRA>
 <JIRA.12752436.1415025713091@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-8245) Cassandra nodes
 periodically die in 2-DC configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Oleg Poleshuk edited comment on CASSANDRA-8245 at 11/4/14 2:26 PM:
-------------------------------------------------------------------

So it happened again (not OOM but Gossip pending tasks).
I ran jstack several times. Not sure if that contains a stacktrace devs need.
If that is not enough just let me know how I can make a proper dump.

Stacktraces are attached.


was (Author: relgames):
So it happened again (not OOM but Gossip pending tasks).
I ran jstack several times. Not sure if that contains a stacktrace devs need.
If that is not enough just let me know how I can make a proper dump.

> Cassandra nodes periodically die in 2-DC configuration
> ------------------------------------------------------
>
>                 Key: CASSANDRA-8245
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8245
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Scientific Linux release 6.5
> java version "1.7.0_51"
> Cassandra 2.0.9
>            Reporter: Oleg Poleshuk
>            Priority: Minor
>         Attachments: stack1.txt, stack2.txt, stack3.txt, stack4.txt, stack5.txt
>
>
> We have 2 DCs with 3 nodes in each.
> Second DC periodically has 1-2 nodes down.
> Looks like it looses connectivity with another nodes and then Gossiper starts to accumulate tasks until Cassandra dies with OOM.
> WARN [MemoryMeter:1] 2014-08-12 14:34:59,803 Memtable.java (line 470) setting live ratio to maximum of 64.0 instead of Infinity
>  WARN [GossipTasks:1] 2014-08-12 14:44:34,866 Gossiper.java (line 637) Gossip stage has 1 pending tasks; skipping status check (no nodes will be marked down)
>  WARN [GossipTasks:1] 2014-08-12 14:44:35,968 Gossiper.java (line 637) Gossip stage has 4 pending tasks; skipping status check (no nodes will be marked down)
>  WARN [GossipTasks:1] 2014-08-12 14:44:37,070 Gossiper.java (line 637) Gossip stage has 8 pending tasks; skipping status check (no nodes will be marked down)
>  WARN [GossipTasks:1] 2014-08-12 14:44:38,171 Gossiper.java (line 637) Gossip stage has 11 pending tasks; skipping status check (no nodes will be marked down)
> ...
> WARN [GossipTasks:1] 2014-10-06 21:42:51,575 Gossiper.java (line 637) Gossip stage has 1014764 pending tasks; skipping status check (no nodes will be marked down)
>  WARN [New I/O worker #13] 2014-10-06 21:54:27,010 Slf4JLogger.java (line 76) Unexpected exception in the selector loop.
> java.lang.OutOfMemoryError: Java heap space
> Also those lines but not sure it is relevant:
> DEBUG [GossipStage:1] 2014-08-12 11:33:18,801 FailureDetector.java (line 338) Ignoring interval time of 2085963047


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)