lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-12055) Enable asynch logging by default
Date Tue, 08 May 2018 14:48:00 GMT

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

Erick Erickson commented on SOLR-12055:
---------------------------------------

[~markrmiller@gmail.com] I'm changing my tune a bit on this, I'm less inclined to make it
the default. On the issue of auditing, would that also apply to logging summary stats rather
than individual messages in some cases?

In particular, depending on the resolution to SOLR-11934 and the like, we might dramatically
reduce the number of log messages. 

So here's what I'm thinking makes the most sense here:

1> as part of the process we'll take a bunch of customer log files and figure out where
the most frequent messages come from. The log file I looked at wasn't particularly representative
so we need a better sample.

2> where it makes sense, publish summary stats at INFO (?) level or change the level

3> provide examples of how to turn on async logging (probably just commented-out sections
of the log4j2.xml files) for those who want it. They can turn on async logging if they want,
we should just make it easy rather than the default.

WDYT?

> Enable asynch logging by default
> --------------------------------
>
>                 Key: SOLR-12055
>                 URL: https://issues.apache.org/jira/browse/SOLR-12055
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: logging
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>            Priority: Minor
>
> When SOLR-7887 is done, switching to asynch logging will be a simple change to the config
files for log4j2. This will reduce contention and increase throughput generally and logging
in particular.
> There's a discussion of the pros/cons here: https://logging.apache.org/log4j/2.0/manual/async.html
> An alternative is to put a note in the Ref Guide about how to enable async logging.
> I guess even if we enable async by default the ref guide still needs a note about how
to _disable_ it.....



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message