You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2018. It is now read-only.
Hi Paulo!
First of all, I want to say thank you for this amazing project.
I'm at the end of building a production grade ES cluster using pretty much all the components you put out here. After updating all the pods with a plugin (recreating every pod), the index templates seem to be deleted. Those templates are stored in ES through the API using a PUT request. Initially, I thought all data is stored only in the data nodes (pods with data role) but it seems like master nodes also need PV to store that kind of data.
Hi Paulo!
First of all, I want to say thank you for this amazing project.
I'm at the end of building a production grade ES cluster using pretty much all the components you put out here. After updating all the pods with a plugin (recreating every pod), the index templates seem to be deleted. Those templates are stored in ES through the API using a PUT request. Initially, I thought all data is stored only in the data nodes (pods with data role) but it seems like master nodes also need PV to store that kind of data.
Referencing this discussion: https://discuss.elastic.co/t/index-template-lost-after-recreate-es-cluster-in-kubernetes-environment/83791
Does it make sense to deploy master pods as StatefulSet as well?
The text was updated successfully, but these errors were encountered: