Details
-
Improvement
-
Status: Open
-
Low
-
Resolution: Unresolved
-
None
-
None
Description
Currently anti-compaction has two log messages forms. They are:
INFO [CompactionExecutor:659] 2016-12-11 03:09:46,553 CompactionManager.java:511 - Starting anticompaction for testks_synchronization.cardticketmap on 0/[] sstables
INFO [CompactionExecutor:658] 2016-12-11 03:09:46,553 CompactionManager.java:511 - Starting anticompaction for testks_synchronization.mapp2pidtouseridreadmodel on 3/[BigTableReader(path='/var/lib/cassandra/data/testks_synchronization/mapp2pidtouseridreadmodel-ebdbe410a43411e6b05641bd36123114/mc-105-big-Data.db'), BigTableReader(path='/var/lib/cassandra/data/testks_synchronization/mapp2pidtouseridreadmodel-ebdbe410a43411e6b05641bd36123114/mc-22-big-Data.db'), BigTableReader(path='/var/lib/cassandra/data/testks_synchronization/mapp2pidtouseridreadmodel-ebdbe410a43411e6b05641bd36123114/mc-17-big-Data.db'), BigTableReader(path='/var/lib/cassandra/data/testks_synchronization/mapp2pidtouseridreadmodel-ebdbe410a43411e6b05641bd36123114/mc-91-big-Data.db'), BigTableReader(path='/var/lib/cassandra/data/testks_synchronization/mapp2pidtouseridreadmodel-ebdbe410a43411e6b05641bd36123114/mc-104-big-Data.db')] sstables
INFO [CompactionExecutor:659] 2016-12-11 03:09:46,554 CompactionManager.java:578 - Completed anticompaction successfully
– or –
INFO [AntiCompactionExecutor:12] 2017-07-02 09:05:42,444 CompactionManager.java:1226 - Performing anticompaction on 1 sstables
INFO [AntiCompactionExecutor:12] 2017-07-02 09:05:42,444 CompactionManager.java:1263 - Anticompacting[BigTableReader(path = '/var/lib/cassandra/data/product_v2/schema_updates-6c7c3d50fe0211e6a001c12716c256ee/mc-21-big-Data.db')]
INFO [AntiCompactionExecutor:12] 2017-07-02 09:05:42,471 CompactionManager.java:1242 - Anticompaction completed successfully, anticompacted from 0 to 1 sstable(s).
It would be nice to have the following:
1) the actual keyspace and table name instead of parsing the SSTable file name
2) IO rate and duration (like in compaction log messages, e.g., 1,028ms = 0.057896MB/s)
3) Partition merge counts (like in compaction log messages, e.g.,
)
This information can be important for creating event timelines and aiding in performance troubleshooting.