You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Kenneth Failbus (JIRA)" <ji...@apache.org> on 2016/08/19 15:48:20 UTC
[jira] [Updated] (CASSANDRA-12506) nodetool compactionhistory in
it's output should have timestamp in human readable form
[ https://issues.apache.org/jira/browse/CASSANDRA-12506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Failbus updated CASSANDRA-12506:
----------------------------------------
Description:
While running nodetool compactionhistory the output shows id and other columns. I wanted to also see the timestamp for each id that got executed in human readable format
So, e.g. in the output if column id can be preceded by timestamp, it will help in understanding when a particular compaction ran and it's impact on the system resources.
was:
While running nodetool compactionhistory the output shows id and other columns. I wanted to also see the timestamp for each id that got executed.
So, e.g. in the output if column id can be preceded by timestamp, it will help in understanding when a particular compaction ran and it's impact on the system resources.
> nodetool compactionhistory in it's output should have timestamp in human readable form
> --------------------------------------------------------------------------------------
>
> Key: CASSANDRA-12506
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12506
> Project: Cassandra
> Issue Type: Improvement
> Components: Compaction
> Environment: AWS
> Reporter: Kenneth Failbus
> Priority: Minor
>
> While running nodetool compactionhistory the output shows id and other columns. I wanted to also see the timestamp for each id that got executed in human readable format
> So, e.g. in the output if column id can be preceded by timestamp, it will help in understanding when a particular compaction ran and it's impact on the system resources.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)