We haven't done any of those recently, on any nodes in this cluster. Would a 
major compaction through 'nodetool compact' cause this? (I think I may have 
done one of those.) 

    On Wednesday, December 7, 2016 4:40 PM, Harikrishnan Pillai 
<hpil...@walmartlabs.com> wrote:
 

 #yiv9834340812 #yiv9834340812 -- P 
{margin-top:0;margin-bottom:0;}#yiv9834340812 This can happen as part of node 
bootstrap,repair or rebuild node.
From: Sotirios Delimanolis <sotodel...@yahoo.com>
Sent: Wednesday, December 7, 2016 4:35:45 PM
To: User
Subject: Huge files in level 1 and level 0 of LeveledCompactionStrategy I have 
a couple of SSTables that are humongous 
-rw-r--r-- 1 user group 138933736915 Dec  1 03:41 
lb-29677471-big-Data.db-rw-r--r-- 1 user group  78444316655 Dec  1 03:58 
lb-29677495-big-Data.db-rw-r--r-- 1 user group 212429252597 Dec  1 08:20 
lb-29678145-big-Data.db
sstablemetadata reports that these are all in SSTable Level 0. This table is 
running with
compaction = {'sstable_size_in_mb': '200', 'tombstone_threshold': '0.25', 
'tombstone_compaction_interval': '300', 'class': 
'org.apache.cassandra.db.compaction.LeveledCompactionStrategy'}
How could this happen?

   

Reply via email to