Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 22 Aug 2012 07:53:42 +1100 (NCT)
From: "Eric Parusel (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <685340429.37097.1345582422235.JavaMail.jiratomcat@arcas>
In-Reply-To: <1134967570.86135.1342882714679.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Comment Edited] (CASSANDRA-4457) Find the cause for the
 need for a larger stack size with jdk 7
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Parusel edited comment on CASSANDRA-4457 at 8/22/12 7:53 AM:
------------------------------------------------------------------

This happened to me too, when I killed one node in the cluster -- the other two nodes threw the following exception:

ERROR [WRITE-/10.40.12.67] 2012-08-21 20:35:29,512 AbstractCassandraDaemon.java (line 134) Exception in thread Thread[WRITE-/10.40.12.67,5,main]
java.lang.StackOverflowError
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
	at java.io.DataOutputStream.flush(DataOutputStream.java:123)
	at org.apache.cassandra.net.OutboundTcpConnection.writeConnected(OutboundTcpConnection.java:156)
	at org.apache.cassandra.net.OutboundTcpConnection.run(OutboundTcpConnection.java:126)

When I bring the 1st node back up the other nodes are unable to send messages to the first node due to the exceptions thrown by the other two nodes on that thread.

After increasing the minimum stack size to 256k this doesn't occur.
                
      was (Author: eparusel):
    This happened to me too, when I killed one node in the cluster -- the other two nodes threw the following exception:

ERROR [WRITE-/10.40.12.67] 2012-08-21 20:35:29,512 AbstractCassandraDaemon.java (line 134) Exception in thread Thread[WRITE-/10.40.12.67,5,main]
java.lang.StackOverflowError
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
	at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
	at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
	at java.io.DataOutputStream.flush(DataOutputStream.java:123)
	at org.apache.cassandra.net.OutboundTcpConnection.writeConnected(OutboundTcpConnection.java:156)
	at org.apache.cassandra.net.OutboundTcpConnection.run(OutboundTcpConnection.java:126)

When I bring the 1st node back up the other nodes are unable to send messages to the first node due to the exception thrown on that thread.

After increasing the minimum stack size to 256k this doesn't occur.
                  
> Find the cause for the need for a larger stack size with jdk 7
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-4457
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4457
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jeremy Hanna
>            Priority: Minor
>
> Based on discussions post CASSANDRA-4275, it appears that on jdk 7 that the minimum stack size needs to be set to something higher than 160k.  That shouldn't be necessary.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira