[
https://issues.apache.org/jira/browse/SOLR-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837389#comment-13837389
]
Ryan Ernst commented on SOLR-5505:
----------------------------------
Thanks for the patch Shikhar. A couple thoughts:
* This forces anyone trying to use the LoggingInfoStream to provide a
loggerName in solrconfig. Could the LIS constructor instead continue using the
local logger if null is passed in? Or have an alternate zero argument
constructor? This way the log4j.properties settings under
solr/example/resources are still relevant.
* You should also update the example solrconfig.xml to include info about the
new setting.
* Could you make the simple case better, where there is only a single log file,
by adding a prefix option to LIS, and adding the core name?
> 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: [email protected]
For additional commands, e-mail: [email protected]
