[
https://issues.apache.org/jira/browse/CASSANDRA-6475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898383#comment-13898383
]
Brian Nixon commented on CASSANDRA-6475:
----------------------------------------
After a discussion with a coworker, I made the connection to bash history files
and the design makes more sense to me. At this point, I'm less concerned about
log splitting than nodetool commands being blocked by a failure to create
logging directories.
To keep our current setup, some parameter will have to be passed since default
behavior will not be able capture the necessary information through our current
environment variables. It would still be nice to have a single parameter to opt
out of logging on nodetool/cassandra-cli/cqlsh or a more descriptive parameter
to direct the tools to our logging directory than user home (that defaults to
user home, if not set).
Note this hits CQL as well since cqlsh uses '~' to initialize its history
logging.
> 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.5#6160)
