[ https://issues.apache.org/jira/browse/CASSANDRA-19760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated CASSANDRA-19760: ---------------------------------------- Test and Documentation Plan: Run a local test, or use cqlsh to see virtual table results. Status: Patch Available (was: Open) > Expose the execution results of a cleanup command to a virtual table > -------------------------------------------------------------------- > > Key: CASSANDRA-19760 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19760 > Project: Cassandra > Issue Type: Improvement > Components: Observability/Metrics > Reporter: Maxim Muzafarov > Assignee: Maxim Muzafarov > Priority: High > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > When a cleanup command is called, the compaction process is triggered under > the hood is triggered accordingly. However, if there is nothing to compact or > the cleanup command returns with a status other than SUCCESSFUL, there is no > way to get the execution results of the command that was run. This is > especially true when using any kind of automation/scripting on top of JMX or > as a nodetool wrapper. > We want to see some information about the cleanup command (id, status, etc.) > that was executed. As a possible solution, we can use a small heap buffer > with the history of the executed commands to expose the buffer in a virtual > table accordingly. > Operations with other OperationType e.g. SCRUB, VERIFY etc. can be exposed in > the same way. -- 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