I figured it out. Another process on that machine was leaking threads.
All is well!
Thanks guys!
Oleg
On 2013-12-16 13:48:39 +, Maciej Miklas said:
the cassandra-env.sh has option
JVM_OPTS=$JVM_OPTS -Xss180k
it will give this error if you start cassandra with java 7. So increase
the
Try using jstack to see if there are a lot of threads there.
Are you using vNodea and Hadoop ?
https://issues.apache.org/jira/browse/CASSANDRA-6169
Cheers
-
Aaron Morton
New Zealand
@aaronmorton
Co-Founder Principal Consultant
Apache Cassandra Consulting
Hi guys!
I beleive my limits settings are correct. Here is the output of ulimits -a:
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i)
the cassandra-env.sh has option
JVM_OPTS=$JVM_OPTS -Xss180k
it will give this error if you start cassandra with java 7. So increase the
value, or remove option.
Regards,
Maciej
On Mon, Dec 16, 2013 at 2:37 PM, srmore comom...@gmail.com wrote:
What is your thread stack size (xss) ? try
