You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Richard Andersen (JIRA)" <ji...@apache.org> on 2017/08/04 20:42:00 UTC
[jira] [Updated] (CASSANDRA-13746) Anti-Compaction log messages do
not have enough information
[ https://issues.apache.org/jira/browse/CASSANDRA-13746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Andersen updated CASSANDRA-13746:
-----------------------------------------
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., {1:1456, })
This information can be important for creating event timelines and aiding in performance troubleshooting.
was:
Currently anti-compaction has two log event 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., {1:1456, })
This information can be important for creating event timelines and aiding in performance troubleshooting.
> Anti-Compaction log messages do not have enough information
> ------------------------------------------------------------
>
> Key: CASSANDRA-13746
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13746
> Project: Cassandra
> Issue Type: Improvement
> Components: Compaction, Core
> Reporter: Richard Andersen
> Priority: Minor
>
> 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., {1:1456, })
> This information can be important for creating event timelines and aiding in performance troubleshooting.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org