[ https://issues.apache.org/jira/browse/SOLR-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413411#comment-16413411 ]
Varun Thacker commented on SOLR-7887: ------------------------------------- Thanks Shalin for pointing it out. You're right we should fix that Before the commit like you pointed out we were keep 10 copies. After the commit we store 7 as that's the default ( I manually tested this and verified it as well) >From the docs ( >https://logging.apache.org/log4j/2.x/manual/appenders.html#FileAppender ) - >"The maximum value of the counter. Once this values is reached older archives >will be deleted on subsequent rollovers. The default value is 7. " So we need something like this for the log4j2.xml file {code} ... <Policies> <OnStartupTriggeringPolicy /> <SizeBasedTriggeringPolicy size="32 MB"/> </Policies> <DefaultRolloverStrategy max="10"/> </RollingFile> ... {code} Secondly, before the commit we were creating log files with this pattern : solr.log , solr.log.1 , solr.log.2 After this commit the file names look like this : solr.log , solr.1.log.*gz*, solr.2.log.*gz* I think we can revert to the old way ? > 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 > Reporter: Shawn Heisey > Assignee: Erick Erickson > Priority: Major > Fix For: 7.4 > > 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, > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org