A catalogue of Cassandra log messages: What is the correct interpretation?
- by knorv
The following is a complete catalogue of all log messages generated by Cassandra 0.6 when stress-testing a Cassandra installation over an extended period of time:
AntiEntropyService: Sending AEService tree for (,) to: []
CassandraDaemon: Binding thrift service to localhost/N.N.N.N:N
CassandraDaemon: Cassandra starting up...
ColumnFamilyStore: has reached its threshold; switching in a fresh Memtable at CommitLogContext(file='.../cassandra/commitlog/CommitLog-N.log', position=N)
ColumnFamilyStore: Enqueuing flush of Memtable()@N
CommitLog: Discarding obsolete commit log:CommitLogSegment(.../cassandra/commitlog/CommitLog-N.log)
CommitLog: Log replay complete
CommitLog: Replaying .../cassandra/commitlog/CommitLog-N.log, ...
CommitLogSegment: Creating new commitlog segment .../cassandra/commitlog/CommitLog-N.log
CompactionManager: Compacted to .../cassandra/data//-N-Data.db. N/N bytes for N keys. Time: Nms.
CompactionManager: Compacting [org.apache.cassandra.io.SSTableReader(path='.../cassandra/data//-N-Data.db'), ...]
DatabaseDescriptor: Auto DiskAccessMode determined to be mmap
GCInspector: GC for ConcurrentMarkSweep: N ms, N reclaimed leaving N used; max is N
GCInspector: GC for ParNew: N ms, N reclaimed leaving N used; max is N
Memtable: Completed flushing .../cassandra/data//-N-Data.db
Memtable: Writing Memtable()@N
SSTable: Deleted .../cassandra/data//-N-Data.db
SSTableDeletingReference: Deleted .../cassandra/data//-N-Data.db
SSTableReader: Sampling index for .../cassandra/data//-N-Data.db
StorageService: Starting up server gossip
SystemTable: Saved ClusterName found: Test Cluster
SystemTable: Saved ClusterName not found. Using Test Cluster
SystemTable: Saved Token found: N
SystemTable: Saved Token not found. Using N
For each of the log messages listed - what is the correct interpretation of the log message?