[ https://issues.apache.org/jira/browse/CASSANDRA-12506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429613#comment-15429613 ]
Arunkumar M commented on CASSANDRA-12506: ----------------------------------------- Compactionhistory is already showing the timestamp in human readable format (compacted_at). >bin/nodetool compactionhistory Compaction History: id keyspace_name columnfamily_name compacted_at bytes_in bytes_out rows_merged 9a9240a0-6766-11e6-ab55-1b95258e9e06 system local 2016-08-20T23:15:05.898 535 293 {4:1} 99c02390-6766-11e6-ab55-1b95258e9e06 system local 2016-08-20T23:15:04.521 506 401 {5:1} Could you please explain further? > nodetool compactionhistory in it's output should have timestamp in human > readable format > ---------------------------------------------------------------------------------------- > > 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 human readable > timestamp format, 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)