[
https://issues.apache.org/jira/browse/ACCUMULO-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222056#comment-13222056
]
Drew Farris commented on ACCUMULO-407:
--------------------------------------
{quote}
1. Do we want to be watching both the *_logger.xml AND the log4j.properties?
{quote}
Yes, because log4j.properties provides a mechanism for influencing the logging
configuration for all applications regardless of whether they have a specific
*_logger.xml or not.
{quote}
2. Do we want to provide a mechanism to pick up the introduction of an
application specific logger.xml file after start up?
{quote}
Would this involve picking up the new application specific configuration file
and disabling the watch on the generic configuration file? This would involve
implementing a custom config file watcher because log4j doesn't seem to have
hooks to cancel a watch initiated by configureAndWatch. An alternative would be
to watch both a generic and application specific logger, but I suspect that
could quickly get confusing.
{quote}
3 . Do we want to continue to have, by default, 2 different logs for each
application, or can we just have 1?
{quote}
How about this: by default the A2 (debug) appender is commented out and default
log level is set to INFO. This would produce 1 log per application. If someone
wants to re-enable DEBUG logging they can uncomment the appender and set the
levels to DEBUG to get the current behavior with 2 files per application OR
they do whatever they they want.
> 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
