[
https://issues.apache.org/jira/browse/CASSANDRA-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660523#comment-13660523
]
Alex Zarutin commented on CASSANDRA-5322:
-----------------------------------------
Hello Sylvain,
Per our discussion, I implemented configurable log4j-server.properties update
(clister wide or per node) with ability to specify Java class and log level.
See the following usage examples for details:
$> ccm node1 setlog TRACE --class com.datastax.whatever
$> ccm setlog TRACE --class com.datastax.whatever
Since, setlog had certain original functionality, I tried to add extra code as
accurate as possible, tested it as much as can, so please take additional look
on them, to make sure, I did not break anything.
In the same time, since updating entire log4j-server.properties has been
already implemented, I just made some fix and refactored code plus implemented
per node functionality (cluster wide has been implemented). See the following
usage examples for details:
$> ccm node3 updatelog4j --path new-log4j-server.properties
$> ccm updatelog4j --path new-log4j-server.properties
Code is checked into my branch (ccm/azarutin), please add the comments
regarding the functionality and style as well ( I am new in Python):
https://github.com/azarutin/ccm/commit/cd496dc6d8687d4805459635315eadcac5ddf85b
Thanks,
Alex
> Make dtest logging more granular
> ---------------------------------
>
> Key: CASSANDRA-5322
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5322
> Project: Cassandra
> Issue Type: Test
> Reporter: Ryan McGuire
> Assignee: Alex Zarutin
>
> From Brandon: We need a way (might need to go in ccm, I haven't looked) to
> just set one class to DEBUG or TRACE, like we'd do in
> conf/log4-server.properties but with an env var preferably, so I can control
> it via buildbot, since it's better at reproducing some issues than I am
> sometimes, but I don't want to run the full hammer debug all the time. Also,
> a way to set Tester.allow_log_errors to false via an env var, since sometimes
> there's an error there that takes a while to fix but is cosmetic, and in the
> meantime I want to catch new failures so we don't fall behind.
--
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
