accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-407) Look into on the fly log4j configuration
Date Fri, 02 Mar 2012 22:48:54 GMT

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

Keith Turner commented on ACCUMULO-407:
---------------------------------------

The reason for having .log and .debug.log file was that sometimes debug messages would fill
the logs files and important errors would be lost.  There are other ways to solve this issue.
 Just wanted to chime in on the reason we have two logs. 
                
> 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