[
https://issues.apache.org/jira/browse/SOLR-12008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16520824#comment-16520824
]
Erick Erickson commented on SOLR-12008:
---------------------------------------
I'm trying to untangle the bits about running examples and have run into this
problem:
Whenever I run an example, I get log files in solr/server/logs. They're small
but annoying. Once the code gets running, then it's fine, the ongoing logs go in
example/techproducts/logs
or
example/node1/logs
example/node2/logs
etc.
The first invocation of SolrCLI creates the bogus logs, in the example cases it
comes back to bin/solr with the -s option which puts the logs in the right
place.
I can't find a good way to just prevent log4j2 from doing _anything_. Absent
that is there a real problem with having the extra log files around in the
example cases?
Varun:
This may be related to your issue with eclipse, we'll see.
I'm also changing
func launch_solr
to
func start_solr
to make it symmetrical.
> Settle a location for the "correct" log4j2.xml file.
> ----------------------------------------------------
>
> Key: SOLR-12008
> URL: https://issues.apache.org/jira/browse/SOLR-12008
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: logging
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Major
> Attachments: SOLR-12008.patch
>
>
> As part of SOLR-11934 I started looking at log4j.properties files. Waaay back
> in 2015, the %C in "/solr/server/resources/log4j.properties" was changed to
> use %c, but the file in "solr/example/resources/log4j.properties" was not
> changed. That got me to looking around and there are a bunch of
> log4j.properties files:
> ./solr/core/src/test-files/log4j.properties
> ./solr/example/resources/log4j.properties
> ./solr/solrj/src/test-files/log4j.properties
> ./solr/server/resources/log4j.properties
> ./solr/server/scripts/cloud-scripts/log4j.properties
> ./solr/contrib/dataimporthandler/src/test-files/log4j.properties
> ./solr/contrib/clustering/src/test-files/log4j.properties
> ./solr/contrib/ltr/src/test-files/log4j.properties
> ./solr/test-framework/src/test-files/log4j.properties
> Why do we have so many? After the log4j2 ticket gets checked in (SOLR-7887) I
> propose the logging configuration files get consolidated. The question is
> "how far"?
> I at least want to get rid of the one in solr/example, users should use the
> one in server/resources. Having to maintain these two separately is asking
> for trouble.
> [[email protected]] Do you have any wisdom on the properties file in
> server/scripts/cloud-scripts?
> Anyone else who has a clue about why the other properties files were created,
> especially the ones in contrib?
> And what about all the ones in various test-files directories? People didn't
> create them for no reason, and I don't want to rediscover that it's a real
> pain to try to re-use the one in server/resources for instance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
