accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Newton (Commented) (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-407) Look into on the fly log4j configuration
Date Thu, 15 Mar 2012 12:43:37 GMT


Eric Newton commented on ACCUMULO-407:

As someone who spends much of his life reading the debug logs, it makes me a little worried
that it is turned off by default.  We can't avoid having the affect the accumulo
processes, so I think we should watch it, too.  Besides, it's a lot easier to edit.  I'm in
favor of watching it, too.

I'll mark this for 1.4.1 and test it for a while.

> Look into on the fly log4j configuration
> ----------------------------------------
>                 Key: ACCUMULO-407
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: John Vines
>            Assignee: Josh Elser
>             Fix For: 1.4.1
>         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:!default.jspa
For more information on JIRA, see:


View raw message