[
https://issues.apache.org/jira/browse/SOLR-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386754#comment-16386754
]
Varun Thacker commented on SOLR-7887:
-------------------------------------
{quote}Are you talking about one of the log4j2.xml files? If so, what I did was
copy the _same_ log4j2.xml file from into three places, example/resources,
server/resources and server/scripts/cloud-scripts.
{quote}
Please don't do that as part of this scope. If you want to tackle that
SOLR-12008 is where we should be doing it
Here's why I feel strongly about not doing that in this patch:
Compare
[https://github.com/apache/lucene-solr/blob/master/solr/server/scripts/cloud-scripts/log4j.properties]
and
[https://github.com/apache/lucene-solr/blob/master/solr/server/resources/log4j.properties]
It's totally different. One if supposed to run cloud script commands and ONLY
has a console appender and NO file logger. Why add a file logger ? And that too
the same file as the solr.log and potentially overwrite it?
> Upgrade Solr to use log4j2 -- log4j 1 now officially end of life
> ----------------------------------------------------------------
>
> Key: SOLR-7887
> URL: https://issues.apache.org/jira/browse/SOLR-7887
> Project: Solr
> Issue Type: Task
> Affects Versions: 5.2.1
> Reporter: Shawn Heisey
> Assignee: Varun Thacker
> Priority: Major
> Attachments: SOLR-7887-WIP.patch, SOLR-7887-eoe-review.patch,
> SOLR-7887-eoe-review.patch, SOLR-7887.patch, SOLR-7887.patch,
> SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch,
> SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch
>
>
> The logging services project has officially announced the EOL of log4j 1:
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> In the official binary jetty deployment, we use use log4j 1.2 as our final
> logging destination, so the admin UI has a log watcher that actually uses
> log4j and java.util.logging classes. That will need to be extended to add
> log4j2. I think that might be the largest pain point to this upgrade.
> There is some crossover between log4j2 and slf4j. Figuring out exactly which
> jars need to be in the lib/ext directory will take some research.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
