As long as solr.xml is a mix of setting that need to be separate per node and cluster wide settings, it makes no sense to enforce it in zk.
Perhaps we instead should stop requiring solr.xml and allow nodes to start without it. Solr can then use a hard coded version as fallback. Most users just copies the example solr.xml into SOLR_HOME so if we can simplify the 80% case I don’t mind if more advanced users put it in zk or in local file system. Jan Høydahl > 1. mar. 2020 kl. 01:26 skrev Erick Erickson <erickerick...@gmail.com>: > > Actually, I do this all the time. However, it’s because I’m always blowing > everything away and installing a different version of Solr or some such, > mostly laziness. > > We should move away from allowing solr.xml to be in SOLR_HOME when running in > cloud mode IMO, but that’ll need to be done in phases. > > Best, > Erick > >> On Feb 28, 2020, at 5:17 PM, Mike Drob <md...@apache.org> wrote: >> >> Hi Searchers! >> >> I was recently looking at some of the start-up logic for Solr and was >> interested in cleaning it up a little bit. However, I'm not sure how common >> certain deployment scenarios are. Specifically is anybody doing the >> following combination: >> >> * Using SolrCloud (i.e. state stored in zookeeper) >> * Loading solr.xml from a local solr home rather than zookeeper >> >> Much appreciated! Thanks, >> Mike
