accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2349) Accumulo should give some notification if there is no *_logger.xml file
Date Thu, 13 Feb 2014 01:04:23 GMT

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

Josh Elser commented on ACCUMULO-2349:
--------------------------------------

DomConfigurator is already used by the code to accomplish this.

I'm still not sure how the current configuration files are a burden on anyone. I rarely even
touch them. Given that the current logging configuration mechanism have been like they are
now for years, I'm don't view them as such a bad thing. They work a given way, and don't require
users to typically touch them. I've also said it once already elsewhere, but you cannot use
log4j.properties to configure the log-forwarding as it currently stands as you cannot configure
the AsyncAppender with it.

Vikram, how are you suggesting that users use the log4j.configuration property to actually
configure per-process logging? That sounds like a bunch of new environment variables? Did
you have something else in mind?

> Accumulo should give some notification if there is no *_logger.xml file
> -----------------------------------------------------------------------
>
>                 Key: ACCUMULO-2349
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2349
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: John Vines
>             Fix For: 1.7.0
>
>
> Right now if you're missing general_logger and the appropriate service_logger, it seems
accumulo just happily carries on with no logs whatsoever. We should alter it to complain loudly
if it's missing them.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message