Setting system_memory_in_mb to 16 GB means the Cassandra heap size you are using is 4 GB. If you meant to use a 16GB heap you should uncomment the line #MAX_HEAP_SIZE="4G" And set MAX_HEAP_SIZE="16G"
You should uncomment the HEAP_NEWSIZE setting as well. I would leave it with the default setting 800M until you are certain it needs to be changed. From: Chamila Wijayarathna [mailto:cdwijayarat...@gmail.com] Sent: Tuesday, July 21, 2015 9:21 PM To: Erick Ramirez Cc: user@cassandra.apache.org Subject: Re: Can't connect to Cassandra server Hi Erick, In cassandra-env.sh, system_memory_in_mb was set to 2GB, I changed it into 16GB, but I still get the same issue. Following are my complete system.log after changing cassandra-env.sh, and new cassandra-env.sh. https://gist.githubusercontent.com/cdwijayarathna/5e7e69c62ac09b45490b/raw/f73f043a6cd68eb5e7f93cf597ec514df7ac61ae/log https://gist.github.com/cdwijayarathna/2665814a9bd3c47ba650 I can't find ant output.log in my cassandra installation. Thanks On Tue, Jul 21, 2015 at 4:31 AM, Erick Ramirez <er...@ramirez.com.au<mailto:er...@ramirez.com.au>> wrote: Chamila, As you can see from the netstat/lsof output, there is nothing listening on port 9042 because Cassandra has not started yet. This is the reason you are unable to connect via cqlsh. You need to work out first why Cassandra has not started. With regards to JVM, Oded is referring to the max heap size and new heap size you have configured. The suspicion is that you have max heap size set too low which is apparent from the heap pressure and GC pattern in the log you provided. Please provide the gist for the following so we can assist: - updated system.log - copy of output.log - cassandra-env.sh Cheers, Erick Erick Ramirez About Me about.me/erickramirezonline<http://about.me/erickramirezonline> -- Chamila Dilshan Wijayarathna, Software Engineer Mobile:(+94)788193620 WSO2 Inc., http://wso2.com/
