accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Drew Farris (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-407) Look into on the fly log4j configuration
Date Sun, 04 Mar 2012 23:34:58 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Drew Farris updated ACCUMULO-407:
---------------------------------

    Attachment: ACCUMULO-407-auto-reload-log4j.patch

Updated patch that does the following:

* Cleans up the foibles
* Watches log4j.properties in the ACCUMULO_HOME/conf directory regardless of whether it exists
at startup.
* Comments out the A2 (debug) appender and sets the log level to INFO by default. 

                
> 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