Skip to content

Conversation

@HoustonPutman
Copy link
Contributor

Fixes #348

This is a change to improve the logic of the managed upgrades, so that the solr operator does not assume that a cloud is completely managed by one SolrCloud resource.

Instead of making sure that # of desired pods = # of live nodes before upgrading the overseer, the operator now just makes sure that all pod names that it manages are accounted for in the cluster's live nodes. This allows for running multiple SolrCloud resources that connect together, while still using the managed restart functionality.

Note this is a fairly small change, but required a lot of refactoring in the tests. That is mostly noise.

@HoustonPutman
Copy link
Contributor Author

@joel-bernstein, could you build this locally and try it out with your setup? The unit tests are pretty comprehensive, but it would be good to have some live testing as well!

@HoustonPutman
Copy link
Contributor Author

(if you can't change the CRDs in your setup, you might want to backport this to release-0.4 and try it out, since there are a fair number of changes in main since the release)

@HoustonPutman
Copy link
Contributor Author

I tested locally and this works well for me. Will merge in a few days

@HoustonPutman HoustonPutman merged commit 7c7f71b into apache:main Oct 22, 2021
@HoustonPutman HoustonPutman deleted the multi-cloud-update branch October 22, 2021 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue with rolling restart with multi SolrCloud clusters

1 participant