cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5823) nodetool history logging
Date Wed, 31 Jul 2013 05:35:48 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724891#comment-13724891
] 

Jason Brown commented on CASSANDRA-5823:
----------------------------------------

bq. perhaps because you run an old version after running a new version. [perhaps only a developer
issue?]

Heh, funny you mention that, because I did run into that today :). However, I suspect once
committed to 1.2 and trunk, everyone (including all us c* devs) won't necessarily be going
back to older versions and running into the older files problem. It's easy enough to check
if the new files exist before copying; I can add in that additional check.

bq. not sure FBUtilities.getHistoryDirectory() is the right name

Agreed. Maybe FBU.getToolsOutputDirectory() ? 
                
> nodetool history logging
> ------------------------
>
>                 Key: CASSANDRA-5823
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5823
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Jason Brown
>            Assignee: Jason Brown
>            Priority: Minor
>             Fix For: 1.2.8, 2.0 rc1
>
>         Attachments: 5823-v1.patch, 5823-v2.patch
>
>
> Capture the commands and time executed from nodetool into a log file, similar to the
cli.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message