Re: Proposal for node configs to adhere to immutable infrastructure

2022-01-24 Thread David Smiley
There is an alternative approach to achieve the aims here, which I think is a bit simpler. No SOLR_VAR env; we don't need it. Instead SOLR_HOME is that. Anything that goes in SOLR_HOME would be resolved with defaulting logic off of SOLR_TIP (solr install dir) at the typical paths from there (e.g

Re: Proposal for node configs to adhere to immutable infrastructure

2021-08-12 Thread David Smiley
For leader/follower, would SOLR_VAR_HOME be adequate? It would mean that, at a minimum, core.properties moves to this data volume as well. If there is a configset, it would either be there directly or better, could be referenced from SOLR_HOME/configsets via referencing a named configset. If suc

Re: Proposal for node configs to adhere to immutable infrastructure

2021-08-12 Thread Jan Høydahl
The SOLR_DATA_HOME was primarily designed for leader/follower mode, letting the user mount a /mnt/my/data/volume into the machines to store indices, but still keep all config locally in a different folder structure. I'm not attached to SOLR_DATA_HOME, it has caused quite some confusion in SolrCl

Re: Proposal for node configs to adhere to immutable infrastructure

2021-08-11 Thread David Smiley
SOLR_DATA_HOME[1] ... yeah that. It allows you to have your cores defined in their typical location yet have the data for all cores be relative to this path -- a different place. You can also set this via "-t" to bin/solr. I'm not sure why someone would want them in separate places. If I recall

Re: Proposal for node configs to adhere to immutable infrastructure

2021-08-11 Thread Jan Høydahl
+1, I've had to work around this by copying newest config from the new container version into the volume on disk, and it is quite confusing. Immutable is good. Jan > 10. aug. 2021 kl. 21:05 skrev David Smiley : > > Folks, please let me know what you think of my proposal below. > > PROBLEM: >

Re: Proposal for node configs to adhere to immutable infrastructure

2021-08-10 Thread Houston Putman
I completely agree with this. The default going forward should be to separate the solr config files and the data directory. It's very inconvenient in Kube that we have to go and copy the config files everytime we start a pod. We should be using the default solr.xml by default, and the docker image

Proposal for node configs to adhere to immutable infrastructure

2021-08-10 Thread David Smiley
Folks, please let me know what you think of my proposal below. PROBLEM: Today in Docker (and probably the Linux installer), the solr home dir in /var/solr/... is initialized with solr.xml, zoo.cfg and log4j2.xml [1]. Consequently, if you deploy new Docker images of Solr with updated built-in confi