accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Drew Farris (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-407) Look into on the fly log4j configuration
Date Tue, 06 Mar 2012 17:10:59 GMT

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

Drew Farris commented on ACCUMULO-407:
--------------------------------------

{quote}
Drew, thanks for the patch. I've added you to our contributor's role in JIRA.
{quote}

Thanks Billie.

{quote}
Drew- my concern with 1 is that we have a property which is initialized in the properties
file, but then overwritten by the xml. If we have reloading on both, we then run the potential
of it periodically change back and forth, which would cause logging inconsistencies. If there
was a way to set a bunch of files to reload with an order of inheritance, that would be awesome.
But I don't think that's supported.
{quote}

John, I can understand your concern, agree and believe that log4j doesn't really do inheritance
of config files. Based on my understanding of what's going on here it seems that {{log4j.properties}}
is used as the default logging configuration at startup prior to calling {{Accumulo.init()}}
which uses the {{DOMConfigurator}} to configure logging. This approach continues to maintain
{{log4j.properties}} as a bootstrap logging configuration and nothing else -- I like that.


The implication here is that the patch should no longer reference the {{PropertyConfigurator}}
for {{log4j.properties}} from the {{Accumulo.init()}} method.
                
> 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, 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