Re: CompactionExecutor holds 8000+ SSTableReader 6G+ memory

2013-06-30 Thread sulong
These two fields: CompressedRandomAccessReader.buffer CompressedRandomAccessReader.compressed in the queue SSTableReader.dfile.pool consumed those memory. I think the SSTableReader.dfile is the cache of the SSTable file. On Sat, Jun 29, 2013 at 1:09 PM, aaron morton wrote: > Lots of memory are

Re: CompactionExecutor holds 8000+ SSTableReader 6G+ memory

2013-06-28 Thread aaron morton
> Lots of memory are consumed by the SSTableReader's cache The file cache is managed by the OS. However the SSTableReader will have bloom filters and compression meta data, both off heap in 1.2. The Key and Row caches are global so not associated with any one SStable. Cheers

Re: CompactionExecutor holds 8000+ SSTableReader 6G+ memory

2013-06-27 Thread sulong
Total 100G data per node. On Fri, Jun 28, 2013 at 2:14 PM, sulong wrote: > aaron, thanks for your reply. Yes, I do use the Leveled compactions > strategy, and the SSTable size is 10M. If it happens again, I will try to > enlarge the sstable size. > > I just wonder why cassandra doesn't limit th

Re: CompactionExecutor holds 8000+ SSTableReader 6G+ memory

2013-06-27 Thread sulong
aaron, thanks for your reply. Yes, I do use the Leveled compactions strategy, and the SSTable size is 10M. If it happens again, I will try to enlarge the sstable size. I just wonder why cassandra doesn't limit the SSTableReader's total memory usage when compacting. Lots of memory are consumed by t

Re: CompactionExecutor holds 8000+ SSTableReader 6G+ memory

2013-06-27 Thread aaron morton
Are you running the Levelled compactions strategy ? If so what is the max SSTable size and what is the total data per node? If you are running it try using a larger SSTable size like 32MB Cheers - Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www

Re: CompactionExecutor holds 8000+ SSTableReader 6G+ memory

2013-06-26 Thread sulong
According to the OpsCenter records, yes, the compaction was running then, 8.5mb /s On Thu, Jun 27, 2013 at 9:54 AM, sulong wrote: > version: 1.2.2 > cluster read requests 800/s, write request 22/s > Sorrry, I don't know whether the compaction was running then. > > > On Thu, Jun 27, 2013 at 1

Re: CompactionExecutor holds 8000+ SSTableReader 6G+ memory

2013-06-26 Thread sulong
version: 1.2.2 cluster read requests 800/s, write request 22/s Sorrry, I don't know whether the compaction was running then. On Thu, Jun 27, 2013 at 1:02 AM, Robert Coli wrote: > On Tue, Jun 25, 2013 at 10:13 PM, sulong wrote: > > I have 4 nodes cassandra cluster. Every node has 32G memory, a

Re: CompactionExecutor holds 8000+ SSTableReader 6G+ memory

2013-06-26 Thread Robert Coli
On Tue, Jun 25, 2013 at 10:13 PM, sulong wrote: > I have 4 nodes cassandra cluster. Every node has 32G memory, and the > cassandra jvm uses 8G. The cluster is suffering from gc. Looks like > CompactionExecutor thread holds too many SSTableReader. See the attachement. What version of Cassandra? Wh