On 9/20/22 14:18, Jan Høydahl wrote:
It has been possible to load solr.xml centrally from zookeeper for a long time.
However, I'm considering deprecating and removing this feature.
Please see https://issues.apache.org/jira/browse/SOLR-15959 for motivation.
My question to the users list is thus - are you loading solr.xml from zookeeper?
And if yes, why is that capability important for you - i.e. could you not
configure it per node?
I have done very little with SolrCloud myself. I converted my tiny
little install to cloud with embedded zk, just the one server, one
collection and one core. I do not have solr.xml in ZK. I did this so I
have access to whatever functionality is cloud-only, should a need ever
arise. I fiddle with that install sometimes to try and answer support
questions. Rebuilding the index only takes about ten minutes, so if I
screw something up I just restore the working config, delete the data
directory, restart, and reindex.
I can see a lot of value in being able to fire up a Solr node with only
/etc/default/solr.in.sh being provided. The solr home can then be
provided completely empty and the node will start, as long as solr.xml
is in ZK.
One thing I think we should do is make it so that Solr starts with some
defaults, if solr.xml is not found at all. We can then bikeshed about
what the defaults should be.
Making it possible for cloud mode to start without solr.xml might remove
most people's need to have it live in ZK. It would make things easier
on docker users ... they would be able to attach a completely empty
volume for the solr home and Solr would start. They might then go back
and add a solr.xml to provide custom settings.
Thanks,
Shawn
