Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uninstalling solr helm chart without uninstalling Zookeeper #665

Open
brickpattern opened this issue Dec 11, 2023 · 3 comments
Open

Uninstalling solr helm chart without uninstalling Zookeeper #665

brickpattern opened this issue Dec 11, 2023 · 3 comments
Labels
question Further information is requested zookeeper Related to Zookeeper or the Zookeeper Operator

Comments

@brickpattern
Copy link

brickpattern commented Dec 11, 2023

hi - this is more of a general Q.

I installed Solrcloud with these options to use a ZK-operator installed seperately.
--set zookeeper-operator.install=false --set zookeeper-operator.use=true

On "helm uninstall solr" ... the ZK pods created using solrcloud say solr-solrcloud-zookeeper-0/1/2 gets deleted as well.

Is there a way to retain the ZK pods created as part of solrcloud and just remove the solr pods?

Alternatively, if i had started off with solrCloud helm chart managing zookeeper pods, how to decouple the ZK from that installation? with operational config files on ZK, can the solrCloud pods be moved off to a standalone ZK?

@HoustonPutman HoustonPutman added question Further information is requested zookeeper Related to Zookeeper or the Zookeeper Operator labels Dec 12, 2023
@HoustonPutman
Copy link
Contributor

So if you deploy Solr using the "provided" zookeeper, then it will be managed in tandem with your SolrCloud. If you want the Zookeeper Cluster's lifecycle to be independent of the Solr lifecycle, you will need to manage it separately.

I would recommend in that case to use the Bitnami Zookeeper Helm chart rather than the Zookeeper Operator's offering.
https://artifacthub.io/packages/helm/bitnami/zookeeper

You would install that by itself, and then find the Zookeeper connection String.
Then in the Solr helm values file, you would use that as the "zk.address" option (and not provide any "zk.provided.*" option).
See the solr helm chart's options for more details: https://artifacthub.io/packages/helm/apache-solr/solr#zk-options

@brickpattern
Copy link
Author

If i had started with inbuilt ZK, would the above approach of specifying zk.address for a standalone ZK will still work?

I would like to retain the data in the solrCloud when cutting over to new ZK.

@janhoy
Copy link
Contributor

janhoy commented Dec 14, 2023

You could call the BACKUP API in order to backup the content from Zookeeper, then RESTORE once you have the new cluster and ZK installed. Or you can find one of the Zookeeper commandline utilities out there (search for it) which will let you backup/restore the content of ZK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested zookeeper Related to Zookeeper or the Zookeeper Operator
Projects
None yet
Development

No branches or pull requests

3 participants