We had the same issue with huge number of sstables on this version and 2.1.3. 
After updating to 2.1.8 the issue slowly faded out (it took a long time for 
Cassandra to compact thousands of sstables)

On Mon, Jul 27, 2015 at 4:05 AM, Peer, Oded <oded.p...@rsa.com> wrote:

> It’s noticeable from the log file that you have many sstable files.
> For instance there are over 11,000 sstable files for table “word_usage”, and 
> over 10,500 of those are less than one MB in size.
> I am guessing this has to be part of the reason bootstrap is taking so long.
> What type of compaction are you using and how did you configure compaction 
> for “word_usage”?
> Which version of Cassandra are you using?
> From: Surbhi Gupta [mailto:surbhi.gupt...@gmail.com]
> Sent: Thursday, July 23, 2015 10:17 PM
> To: user@cassandra.apache.org
> Cc: Erick Ramirez
> Subject: Re: Can't connect to Cassandra server
> What is the output you are getting if you are issuing nodetool status command 
> ...
> On 23 July 2015 at 11:30, Chamila Wijayarathna 
> <cdwijayarat...@gmail.com<mailto:cdwijayarat...@gmail.com>> wrote:
> Hi Peer,
> I changed cassandra-env.sh and following are the parameters I used,'
> MAX_HEAP_SIZE="8G"
> HEAP_NEWSIZE="1600M"
> But I am still unable to start the server properly. But this time system.log 
> has bit different logs.
> https://gist.github.com/cdwijayarathna/75f65a34d9e71829adaa
> Any idea on how to proceed?
> Thanks
> On Wed, Jul 22, 2015 at 11:54 AM, Peer, Oded 
> <oded.p...@rsa.com<mailto:oded.p...@rsa.com>> wrote:
> 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<mailto:cdwijayarat...@gmail.com>]
> Sent: Tuesday, July 21, 2015 9:21 PM
> To: Erick Ramirez
> Cc: user@cassandra.apache.org<mailto: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<tel:%28%2B94%29788193620>
> WSO2 Inc., http://wso2.com/
> --
> Chamila Dilshan Wijayarathna,
> Software Engineer
> Mobile:(+94)788193620
> WSO2 Inc., http://wso2.com/

Reply via email to