[
https://issues.apache.org/jira/browse/ACCUMULO-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated ACCUMULO-407:
--------------------------------
Fix Version/s: 1.4.0
Affects Version/s: 1.4.0
Status: Patch Available (was: Open)
Simple patch that appears to enable dynamic reloading of conf/*_logging.xml and
conf/log4j.properties.
> 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
