incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Viktor Jevdokimov <>
Subject RE: Error during startup - java.lang.OutOfMemoryError: unable to create new native thread
Date Tue, 10 Sep 2013 05:46:56 GMT
For start:
- check ( -Xss size, you may need to increase it for your JVM;
- check ( -Xms and -Xmx size, you may need to increase it for your data load/bloom
filter/index sizes.

Best regards / Pagarbiai
Viktor Jevdokimov
Senior Developer

[Adform News] <>

Visit us at Dmexco: Hall 6 Stand B-52
September 18-19 Cologne, Germany

Phone: +370 5 212 3063, Fax +370 5 261 0453
J. Jasinskio 16C, LT-03163 Vilnius, Lithuania
Follow us on Twitter: @adforminsider<!/adforminsider>
Take a ride with Adform's Rich Media Suite<>

[Dmexco 2013] <>

Disclaimer: The information contained in this message and attachments is intended solely for
the attention and use of the named addressee and may be confidential. If you are not the intended
recipient, you are reminded that the information remains the property of the sender. You must
not use, disclose, distribute, copy, print or rely on this e-mail. If you have received this
message in error, please contact the sender immediately and irrevocably delete this message
and any copies.

From: srmore []
Sent: Tuesday, September 10, 2013 6:16 AM
Subject: Error during startup - java.lang.OutOfMemoryError: unable to create new native thread

I have a 5 node cluster with a load of around 300GB each. A node went down and does not come
up. I can see the following exception in the logs.

ERROR [main] 2013-09-09 21:50:56,117 (line 139) Fatal exception
in thread Thread[main,5,main]
java.lang.OutOfMemoryError: unable to create new native thread
        at java.lang.Thread.start0(Native Method)
        at java.lang.Thread.start(
        at java.util.concurrent.ThreadPoolExecutor.addIfUnderCorePoolSize(
        at java.util.concurrent.ThreadPoolExecutor.prestartAllCoreThreads(
        at org.apache.cassandra.concurrent.JMXEnabledThreadPoolExecutor.<init>(
        at org.apache.cassandra.concurrent.JMXEnabledThreadPoolExecutor.<init>(
        at org.apache.cassandra.concurrent.JMXConfigurableThreadPoolExecutor.<init>(
        at org.apache.cassandra.concurrent.StageManager.multiThreadedConfigurableStage(
        at org.apache.cassandra.concurrent.StageManager.<clinit>(
        at org.apache.cassandra.db.commitlog.CommitLog.recover(
        at org.apache.cassandra.db.commitlog.CommitLog.recover(

The ulimit -u output is
Which is far more than what is recommended [1] (10240) and I am skeptical to set it to unlimited
as recommended here [2]
Any pointers as to what could be the issue and how to get the node up.


Thanks !

View raw message