All:

Why cassandra crash after print the following log?

 

INFO [SSTABLE-CLEANUP-TIMER] 2011-06-16 14:19:01,020
SSTableDeletingReference.java (line 104) Deleted
/usr/local/rss/DDB/data/data/PSCluster/CsiStatusTab-206-Data.db

 INFO [SSTABLE-CLEANUP-TIMER] 2011-06-16 14:19:01,020
SSTableDeletingReference.java (line 104) Deleted
/usr/local/rss/DDB/data/data/PSCluster/CsiStatusTab-207-Data.db

 INFO [SSTABLE-CLEANUP-TIMER] 2011-06-16 14:19:01,020
SSTableDeletingReference.java (line 104) Deleted
/usr/local/rss/DDB/data/data/PSCluster/VCCCurScheduleTable-137-Data.db

 INFO [SSTABLE-CLEANUP-TIMER] 2011-06-16 14:19:01,021
SSTableDeletingReference.java (line 104) Deleted
/usr/local/rss/DDB/data/data/PSCluster/CsiStatusTab-205-Data.db

 INFO [SSTABLE-CLEANUP-TIMER] 2011-06-16 14:19:01,021
SSTableDeletingReference.java (line 104) Deleted
/usr/local/rss/DDB/data/data/PSCluster/VCCCurScheduleTable-139-Data.db

 INFO [SSTABLE-CLEANUP-TIMER] 2011-06-16 14:19:01,021
SSTableDeletingReference.java (line 104) Deleted
/usr/local/rss/DDB/data/data/PSCluster/VCCCurScheduleTable-138-Data.db

 INFO [SSTABLE-CLEANUP-TIMER] 2011-06-16 14:19:01,021
SSTableDeletingReference.java (line 104) Deleted
/usr/local/rss/DDB/data/data/PSCluster/CsiStatusTab-208-Data.db

 INFO [GC inspection] 2011-06-16 14:22:59,562 GCInspector.java (line
110) GC for ParNew: 385 ms, 26859800 reclaimed leaving 117789112 used;
max is 1187840000

 

 

Best Regards

Donna li

Reply via email to