[
https://issues.apache.org/jira/browse/ACCUMULO-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211194#comment-13211194
]
David Medinets commented on ACCUMULO-407:
-----------------------------------------
Does this property file change need to be done on all nodes in the cluster? Do
you think it would be hard to have log4j read from an hdfs file? Also note that
Accumulo might be running in an environment in which the files are all 'locked
down' (i.e. unchangeable). In the past, I have written a small web interface to
change the log levels. The web application writes the log4j property file.
> Look into on the fly log4j configuration
> ----------------------------------------
>
> Key: ACCUMULO-407
> URL: https://issues.apache.org/jira/browse/ACCUMULO-407
> Project: Accumulo
> Issue Type: Improvement
> Affects Versions: 1.4.0
> Reporter: John Vines
> Assignee: Josh Elser
> Fix For: 1.4.0
>
> Attachments: ACCUMULO-407-auto-reload-log4j.patch
>
>
> For long running systems, logs may not want to be kept at the debug level
> 24/7. But there may be times where a single long query may be want to looked
> into without cycling the entire systems. We think it may be possible to make
> log4j configurable on fly, so lets start by looking into how difficult it
> will be.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
