Hi,
We are using 2.0.3 and vnodes. After every repair -pr operation  50+ tiny 
sstables( <10K) get created. And these sstables never get compacted due to 
coldness issue. I have raised 
https://issues.apache.org/jira/browse/CASSANDRA-9146 for this issue but I have 
been told to upgrade. Till we upgrade to latest 2.0.x , we are stuck. Upgrade 
takes time, testing and planning in Production systems :(

I have observed that even if vnodes are NOT damaged, hundreds of tiny sstables 
are created during repair for a wide row CF. This is beyond my understanding. 
If everything is consistent, and for the entire repair process Cassandra is 
saying "Endpoints /x.x.x.x and /x.x.x.y are consistent for <CF>". Whats the 
need of creating sstables?
Is there any alternative to regular major compaction to deal with situation? 


ThanksAnuj Wadehra

Reply via email to