You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/12/20 00:32:07 UTC

[jira] [Updated] (CASSANDRA-6475) Control nodetool history logging directory

     [ https://issues.apache.org/jira/browse/CASSANDRA-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-6475:
--------------------------------------

         Priority: Trivial  (was: Minor)
    Fix Version/s:     (was: 2.0.4)
                       (was: 1.2.13)
           Labels: lhf  (was: )

> Control nodetool history logging directory
> ------------------------------------------
>
>                 Key: CASSANDRA-6475
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6475
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Brian Nixon
>            Priority: Trivial
>              Labels: lhf
>
> Nodetool history is logged to a directory based on the current user home. This leads to splintering of history with more than one user and, in one case, a failure to run any nodetool commands as the user did not have write access to their home directory.
> Suggested fix is to make the base directory for the history logging (both nodetool and cli) configurable. A way to disable the logging of these tools would also help.
> Reference:
> https://issues.apache.org/jira/browse/CASSANDRA-5823



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)