[
https://issues.apache.org/jira/browse/CASSANDRA-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660505#comment-13660505
]
Alex Zarutin commented on CASSANDRA-5322:
-----------------------------------------
I saw set_log_level(), however the problem is much more complex. Controlling
logging level over set_log_level() method (even we slightly update it) is just
the very tiny part of what can be controlled using log4j configuration. The way
I see future usage is _at least_ adding logging for the specific classes,
appenders, and set_log_level() is obviously does not provide this
functionality. I can understand that we can write log4j format dumper, but I
guess it is overkill for now, plus it needs to be well designed.
There are two options of archive this:
I) Edit log4j-server.properties externally, copy under conf, and start the
cassandra. Or we can add log4j Automatic Reconfiguration,
http://logging.apache.org/log4j/2.x/manual/configuration.html#AutomaticReconfiguration
and we would not need to re-start the Cassandra
II) Control log4j-server.properties over JMX,
http://logging.apache.org/log4j/2.x/manual/jmx.html but is supported in log4j
version 2 only when we use version 1.2.16
What I mean by this, is that we would probably need to live with changing
log4j-server.properties manually for some time. But, I got that you are OK with
updating ccm to perform log4j update rather than do it inside the test using
build-in python methods.
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
