Return-Path: 
 <dev-return-153499-apmail-lucene-dev-archive=lucene.apache.org@lucene.apache.org>
X-Original-To: apmail-lucene-dev-archive@www.apache.org
Delivered-To: apmail-lucene-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3339D10699
	for <apmail-lucene-dev-archive@www.apache.org>;
 Tue,  3 Dec 2013 16:30:49 +0000 (UTC)
Received: (qmail 92612 invoked by uid 500); 3 Dec 2013 16:30:38 -0000
Delivered-To: apmail-lucene-dev-archive@lucene.apache.org
Received: (qmail 92377 invoked by uid 500); 3 Dec 2013 16:30:38 -0000
Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@lucene.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@lucene.apache.org>
List-Post: <mailto:dev@lucene.apache.org>
List-Id: <dev.lucene.apache.org>
Reply-To: dev@lucene.apache.org
Delivered-To: mailing list dev@lucene.apache.org
Received: (qmail 92337 invoked by uid 99); 3 Dec 2013 16:30:37 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Dec 2013 16:30:37 +0000
Date: Tue, 3 Dec 2013 16:30:37 +0000 (UTC)
From: "Shikhar Bhushan (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12681134.1385414804854.62696.1386088237083@arcas>
In-Reply-To: <JIRA.12681134.1385414804854@arcas>
References: <JIRA.12681134.1385414804854@arcas>
Subject: [jira] [Commented] (SOLR-5505) LoggingInfoStream not usabe in a
 multi-core setup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Shikhar Bhushan commented on SOLR-5505:
---------------------------------------

Hi Ryan,

* If the loggerName attribute is missing, it defaults to the fully-qualified class name of LoggingInfoStream (see default value used for getting the attribute).

* I will update the example solrconfig.xml, good call!

* Even if the logs are being sent to the same file, the logger name is almost always part of the formatter configuration. For the solrconfig.xml perhaps a good example would be {{<infoStream loggerName="org.apache.solr.update.LoggingInfoStream.${solr.core.name}">}} (I _think_ that actually will substitute core name correctly, will check...).

> LoggingInfoStream not usabe in a multi-core setup
> -------------------------------------------------
>
>                 Key: SOLR-5505
>                 URL: https://issues.apache.org/jira/browse/SOLR-5505
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.6
>            Reporter: Shikhar Bhushan
>         Attachments: SOLR-5505.patch
>
>
> {{LoggingInfoStream}} that was introduced in SOLR-4977 does not log any core context.
> Previously this was possible by encoding this into the infoStream's file path.
> This means in a multi-core setup it is very hard to distinguish between the infoStream messages for different cores.
> {{LoggingInfoStream}} should be automatically configured to prepend the core name to log messages.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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