I'm already seeing some value from my Solr upgrade test automation -- https://github.com/apache/solr/pull/3706
I see that Solr 9 & 10 (at least when Dockerized) put a log4j2.xml (a config file) into /var/solr/log4j2.xml. Note the volume is /var/solr and of course is intended for data. This is a config file. Moving on... Solr 9 writes its config file with "solr.log.dir" var substitution but Solr 10 renamed that to "solr.logs.dir". When Solr 10 takes over this volume, it successfully starts but nonetheless its console logs are spewing error messages about it not being able to resolve solr.log.dir. I know we've got some nifty EnvUtils sys prop deprecation migration but that would only work if an old property is passed into the VM; it doesn't help when a config file has old references, like here. In this case I'd like to see if we can get that log4j2.xml file out of there, using one in the r/o Docker container, not in the volume. It doesn't belong there IMO. Proposal is to remove this: https://github.com/apache/solr/blob/0fb94f7b38e7a7b735ce97ad8d19412e5fbd1f93/solr/docker/scripts/init-var-solr#L59 and add/edit other stuff TBD. ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley
