[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18268: -- Authors: Milan Krisko, Stefan Miklosovic (was: Milan Krisko) Fix Version/s: 5.0 Source Control Link: https://github.com/apache/cassandra/commit/180f0f0b5b47a48c1a7d88927223cc52871cc801 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > Fix For: 5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18268: -- Reviewers: Brad Schoening, Brandon Williams, Kan Maung (was: Brandon Williams, Kan Maung, Stefan Miklosovic) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > Fix For: 5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18268: -- Reviewers: Brandon Williams, Kan Maung, Stefan Miklosovic (was: Brandon Williams, Stefan Miklosovic) Status: Review In Progress (was: Patch Available) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18268: -- Status: Ready to Commit (was: Review In Progress) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > Time Spent: 10m > Remaining Estimate: 0h > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18268: - Reviewers: Brandon Williams, Stefan Miklosovic (was: Stefan Miklosovic) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18268: -- Status: Patch Available (was: In Progress) I took Milan's work here. [https://github.com/apache/cassandra/pull/2174] and put some minor improvements with his agreement to speed up things here [https://github.com/apache/cassandra/pull/2184] > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18268: -- Status: In Progress (was: Changes Suggested) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18268: -- Reviewers: Stefan Miklosovic Status: Review In Progress (was: Patch Available) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18268: -- Status: Changes Suggested (was: Review In Progress) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milan Krisko updated CASSANDRA-18268: - Status: Patch Available (was: Open) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18268: - Status: Open (was: Patch Available) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milan Krisko updated CASSANDRA-18268: - Test and Documentation Plan: https://github.com/apache/cassandra/pull/2174 Status: Patch Available (was: Open) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Assignee: Milan Krisko >Priority: Normal > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18268) Log completed status with cleanup and garbagecollect operations
[ https://issues.apache.org/jira/browse/CASSANDRA-18268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18268: - Change Category: Operability Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Log completed status with cleanup and garbagecollect operations > --- > > Key: CASSANDRA-18268 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18268 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Logging >Reporter: Kan Maung >Priority: Normal > > Whenever a cleanup or garbagecollect operation is issued from nodetool, there > is no log statuses for the start and end of the operation at the node level > although statuses on individual sstables are captured. Start can be inferred, > but it is difficult to know when the operation has completed because there is > no log message. > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable1 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable1 successfully > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:353 - > Starting Remove deleted data for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:364 - No > sstables to GARBAGE_COLLECT for keyspace1.sstable2 > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 - > Finished Remove deleted data for keyspace1.sstable2 successfully > > This improvement proposes adding additional for start and end statuses log > messages for the above operation at the node level. I.e., > > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Starting GARBAGE_COLLECT > …. > [INFO ] cluster_id=5 ip_address=127.1.1.1 CompactionManager.java:395 – > Completed GARBAGE_COLLECT -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
