cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Nixon (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6475) Control nodetool history logging directory
Date Mon, 10 Feb 2014 21:21:21 GMT


Brian Nixon commented on CASSANDRA-6475:

Yes, we can and do hand the logging directory to the nodetool command as -Duser.home. It's
simply awkward, unintuitive, and inconvenient when coordinating the access of multiple users
to a single Cassandra instance.

Is there a compelling reason to (1) leave nodetool and cli history logging rooted at user_home
or (2) not have a property to turn off history logging completely if it is not desired?

> Control nodetool history logging directory
> ------------------------------------------
>                 Key: CASSANDRA-6475
>                 URL:
>             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:

This message was sent by Atlassian JIRA

View raw message