Here are some of the things I do to facilitate upgrades: 1) Script out my steps using the various API’s available to Solr. 2) Use SolrCloud, it makes life easier in decoupling where data is stored from the logical structure of my collections. 3) Adopts some of the “configuration as code” ideas in DevOps to manage all of those settings.
If you are open to Kubernetes, the https://solr.apache.org/operator/ <https://solr.apache.org/operator/> is also meant to make handling all those configuration values simpler to deal with. Eric > On Jul 20, 2021, at 8:09 AM, Scott Hollenbeck > <s...@musclecarresearch.com.INVALID> wrote: > > Can anyone share some thoughts on best practices for upgrading a solr node > and preserving my TLS settings and core configurations while doing so? Mya > existing installation has two cores with support for basic authentication > and TLS properly configured and working. In the past, I've done my upgrades > by running the service installation script (bin/install_solr_service.sh) > this way: > > $ /opt/install_solr_service.sh /opt/solr-8.9.0.tgz -f -n > > That installs the new release and re-creates a symlink to the new directory, > but I have to manually re-create the configurations for my cores, move the > keystore and security.json files, and re-edit bin/solr.in.sh to change the > TLS/SSL settings. There has to be a better way - what am I missing? > > Scott > _______________________ Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | My Free/Busy <http://tinyurl.com/eric-cal> Co-Author: Apache Solr Enterprise Search Server, 3rd Ed <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> This e-mail and all contents, including attachments, is considered to be Company Confidential unless explicitly stated otherwise, regardless of whether attachments are marked as such.
