Re: High Heap Memory usage during nodetool repair in Cassandra 3.0.3

Thanks Markus that may have helped the cause as well. Certainly repair works great beyond 3.0.3 and we have tested it on 3.5+ as well as on 3.0.7. On that note, it is evident that there are been a number of optimizations on various fronts post 3.0.3, I would like to know the general opinion about

Re: High Heap Memory usage during nodetool repair in Cassandra 3.0.3

it could also be CASSANDRA-11412 if you have many sstables and vnodes On Wed, Jun 22, 2016 at 2:50 PM, Bhuvan Rawal wrote: > Thanks for the info Paulo, Robert. I tried further testing with other > parameters and it was prevalent. We could be either 11739, 11206. But im >

Re: High Heap Memory usage during nodetool repair in Cassandra 3.0.3

Thanks for the info Paulo, Robert. I tried further testing with other parameters and it was prevalent. We could be either 11739, 11206. But im spektical about 11739 because repair works well in 3.5 and 11739 seems to be fixed for 3.7/3.0.7. We may possibly resolve this by increasing heap size

Re: High Heap Memory usage during nodetool repair in Cassandra 3.0.3

We have tried this with 3.5 and there also heap usage was optimized as in 3.7. Though we have to roll-back from 3.5 to 3.0.3 due to CASSANDRA-11513 .

Re: High Heap Memory usage during nodetool repair in Cassandra 3.0.3

You could also be hitting CASSANDRA-11739, which was fixed on 3.0.7 and could potentially cause OOMs for long-running repairs. 2016-06-20 13:26 GMT-03:00 Robert Stupp : > One possibility might be CASSANDRA-11206 (Support large partitions on the > 3.0 sstable format), which

Re: High Heap Memory usage during nodetool repair in Cassandra 3.0.3

One possibility might be CASSANDRA-11206 (Support large partitions on the 3.0 sstable format), which reduces heap usage for other operations (like repair, compactions) as well. You can verify that by setting column_index_cache_size_in_kb in c.yaml to a really high value like 1000 - if you