You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2012/10/24 22:52:12 UTC
[jira] [Resolved] (CASSANDRA-4856) Thrift daemon is crashing the
server
[ https://issues.apache.org/jira/browse/CASSANDRA-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams resolved CASSANDRA-4856.
-----------------------------------------
Resolution: Invalid
"unable to create new native thread" means the OS denied java. It was probably related to your OS upgrade somehow.
> Thrift daemon is crashing the server
> ------------------------------------
>
> Key: CASSANDRA-4856
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4856
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.6
> Environment: MacOS 10.8.2
> Reporter: Michael Yeh
>
> I'm new to cassandra and was looking at using the kundera thrift client. I was able to get the sample code working without any issues. After upgrading to mountain lion on my mac, I didn't realize I had lost the /var/lib/cassandra directory. When I tried to run the previously working sample code, it would crash cassandra with the following stack trace:
> INFO 12:55:37,147 Listening for thrift clients...
> ERROR 12:55:43,545 Exception in thread Thread[Thread-3,5,main]
> java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start0(Native Method)
> at java.lang.Thread.start(Thread.java:658)
> at java.util.concurrent.ThreadPoolExecutor.addIfUnderMaximumPoolSize(ThreadPoolExecutor.java:727)
> at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:657)
> at org.apache.cassandra.thrift.CustomTThreadPoolServer.serve(CustomTThreadPoolServer.java:103)
> at org.apache.cassandra.thrift.CassandraDaemon$ThriftServer.run(CassandraDaemon.java:213)
> After realizing that I needed to recreate the keyspace and column families, everything started to work again. Although I'm no longer blocked with my issue, no clients should ever be able to crash a server even if it is user error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira