accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-407) Look into on the fly log4j configuration
Date Sat, 03 Mar 2012 01:42:55 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221449#comment-13221449
] 

Josh Elser commented on ACCUMULO-407:
-------------------------------------

0. Sorry, John. I saw I had borked the patch earlier this week but hadn't taken the time to
push a new one.

1-3. I don't think we know what exactly the best logging management solution is given the
amount of chatter I see above. So, I concur with you John: a complete solution isn't ready
for 1.4.0. However, I do believe that the $ACCUMULO_HOME/conf/generic_logger.xml should be
auto-reloaded with the configureAndWatch. It is highly undesirable to leave verbose iterator
logging enabled on a multi-user system, but at the same time, it's also a non-starter to have
to bounce Accumulo to get those verbose logging statements when trying to debug some unknown
issue.

IMO, the best short term solution would be to merge the DOMConfigurator.configureAndWatch(logConfig,
5000) change into the 1.4 (and thus 1.4.0), and then decide what the best action to take would
be for 1.4.1+/1.5.
                
> 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

        

Mime
View raw message