Troubleshooting
Problem
Insufficient resource limits can result in a number of errors in Apache Cassandra, DSE, and OpsCenter, such as the following:
Errors/Warns to Observe
In Apache Cassandra due to insufficient as (address space) or memlock setting:
ERROR [SSTableBatchOpen:1] 2012-07-25 15:46:02,913 AbstractCassandraDaemon.java (line 139) Fatal exception in thread Thread[SSTableBatchOpen:1,5,main] java.io.IOError: java.io.IOException: Map failed at
In Apache Cassandra due to insufficient memlock settings:
WARN [main] 2011-06-15 09:58:56,861 CLibrary.java (line 118) Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out, especially with mmapped I/O enabled. Increase RLIMIT_MEMLOCK or run Apache Cassandra as root.
In Apache Cassandra due to insufficient nofiles setting:
WARN 05:13:43,644 Transport error occurred during acceptance of message. org.apache.thrift.transport.TTransportException: java.net.SocketException: Too many open files
In Apache Cassandra due to insufficient nofiles setting:
ERROR [MutationStage:11] 2012-04-30 09:46:08,102 AbstractCassandraDaemon.java (line 139) Fatal exception in thread Thread[MutationStage:11,5,main] java.lang.OutOfMemoryError: unable to create new native thread
In OpsCenter, due to insufficient nofiles:
2012-08-13 11:22:51-0400 [] INFO: Could not accept new connection (EMFILE)
These settings can be permanently set via the /etc/security/limits.conf file. You can view the limits using the 'ulimit -a' command, and they can also be temporarily set using this command. The following are recommended limits settings for your limits.conf file when using Apache Cassandra and OpsCenter:
* soft nofile 32768 * hard nofile 32768 root soft nofile 32768 root hard nofile 32768 * soft memlock unlimited * hard memlock unlimited root soft memlock unlimited root hard memlock unlimited * soft as unlimited * hard as unlimited root soft as unlimited root hard as unlimited
In addition, you may need to run the following command to enable more mapping (at the command line; do not add to limits.conf file):
sysctl -w vm.max_map_count = 1048575
The following error can indicate the need to increase max_map_count:
Java HotSpot(TM) 64-Bit Server VM warning: Attempt to allocate stack guard pages failed. Last reviewed 2023/11/29
Document Location
Worldwide
Historical Number
ka06R000000HdIEQA0
Was this topic helpful?
Document Information
Modified date:
30 January 2026
UID
ibm17258843