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

Ephemeral storage should extend to ZK instance #259

Closed
mogul opened this issue Apr 19, 2021 · 2 comments · Fixed by #284
Closed

Ephemeral storage should extend to ZK instance #259

mogul opened this issue Apr 19, 2021 · 2 comments · Fixed by #284
Labels
zookeeper Related to Zookeeper or the Zookeeper Operator
Milestone

Comments

@mogul
Copy link
Contributor

mogul commented Apr 19, 2021

When you specify the ephemeral storage type for a solrcloud, that should also extend to the Zookeeper instance that the solr-operator manages (specified like this).

(We noted this when the ZK pod did not start on AWS Fargate because it was trying to use a persistent volume claim, so the SolrCloud pod did not start either despite using emptyDir.)

@HoustonPutman
Copy link
Contributor

Agreed. This is a good feature that should be included in v0.4.0.

We should expose all options for the Zookeeper storage, but default to ephemeral/persistent depending on what the SolrCloud uses.

@HoustonPutman HoustonPutman added the zookeeper Related to Zookeeper or the Zookeeper Operator label Apr 23, 2021
@jward-bw
Copy link
Contributor

We should expose all options for the Zookeeper storage, but default to ephemeral/persistent depending on what the SolrCloud uses.

This is important, in our use-case we probably will have solr data on ephemeral but ZK on persistent.

@HoustonPutman HoustonPutman changed the title Ephermeral storage should extend to ZK instance Ephemeral storage should extend to ZK instance Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
zookeeper Related to Zookeeper or the Zookeeper Operator
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants