ArbitraryCritter commented on PR #827: URL: https://github.com/apache/solr-operator/pull/827#issuecomment-4404945392
Just tested this on our 3 node staging cluster, which sees a reasonable test load, I'll keep it running in this configuration for ~a week and report any issues we may see. Cluster state before start: solr-operator: 0.9.1 solr: 9.10 Process: - I first upgraded the solr-operator without any other modification (eg. helm chart and solr-operator image built from this branch). - Upgraded the solr cluster to 10.0 based image (with some custom modules) Findings: There were no issues with upgrading the solr-operator itself, that just worked. Only thing to note is that the SolrMajorVersion seems to default to 9, which seems quite sane, but also slightly different from what is mentioned in the PR description, I'd expected it to complain that I needed to set a version to proceed. As is noted in the issue, the prometheusExporter is gone from Solr 10 and upgrading with it will not work, it has to be disabled first. Failing to remove it caused the upgrade process to stall, requiring a rollback. The SOLR_MODULES behavior seems a bit different with the new solr helm chart. We've been using a custom docker image that contains a solr module specific for own environment (used for access checks). We've been overriding the SOLR_MODULES env directly in the dockerfile. Before the solr helm chart upgrade the SOLR_MODULES variables wasn't set by the helmchart, after the upgrade it was (with the value SOLR_MODULES=s3-repository). This was easily remedied by adding the appropriate modules to "solrOptions.SolrModules", but it does seem that something about the SolrModules env behaves a bit differently in the new solr chart. I don't think this is a bug, it's probably more us misusing the SOLR_MODULES concept by overriding it in the Dockerfile rather than the helm chart, but perhaps a note should be added to the release that users should be sure to define the solr modules they use through the helm chart (or something similar). All in all this seems to work as expected. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
