[
https://issues.apache.org/jira/browse/CASSANDRA-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne resolved CASSANDRA-7046.
-----------------------------------------
Resolution: Won't Fix
I agree with Brandon here: you can get this with either a trivial shell script
or by checking {{~/.cassandra/nodetool.history}}. I'll add that printing that
by default could potentially break scripts (and makes it painful for scripts in
general) and adding a option for something that can trivially be done otherwise
strongly feels like clutter. Sorry but closing.
> Update nodetool commands to output the date and time they were run on
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-7046
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7046
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Johnny Miller
> Assignee: Clément Lardeur
> Priority: Trivial
> Labels: lhf
> Attachments: trunk-7046-v1.patch
>
>
> It would help if the various nodetool commands also outputted the system date
> time they were run. Often these commands are executed and then we look at the
> cassandra log files to try and find out what was happening at that time.
> This is certainly just a convenience feature, but it would be nice to have
> the information in there to aid with diagnostics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
