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 Sun, 09 Feb 2014 02:06:19 GMT


Brian Nixon commented on CASSANDRA-6475:

I'm using version 1.2.13 and expect the same error from 2.0. The attached error is thrown
because the specific user running the tool does not have write permission on /. 

Write permissions aside, it would be a useful feature to be able to write the history logs
to a common logging directory without having to change user_home.

Exception in thread "main" FSWriteError in /.cassandra
	at org.apache.cassandra.utils.FBUtilities.getToolsOutputDirectory(
	at org.apache.cassandra.cli.CliClient$CfAssumptions.<init>(
	at org.apache.cassandra.cli.CliClient.<init>(
	at org.apache.cassandra.cli.CliMain.connect(
	at org.apache.cassandra.cli.CliMain.main(
Caused by: Failed to mkdirs /.cassandra
	... 6 more

> 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