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
We currently require a strict node role mapping while attempting to reuse PVCs.
This helps us make sure a master node does not get assigned a data volume, and the other way around.
However consider the following case:
3 master-data nodes
the user enables the ML role on all nodes
Currently we'll not reuse PVCs for those 3 ML nodes, and go through data migration. But we could reuse PVCs. Should we also reuse PVCs the other way around (data-ML become data only)?
The text was updated successfully, but these errors were encountered:
We decided to rely on one StatefulSet per NodeSpec in the Elasticsearch CRD.
PVC reuse is now limited to NodeSpecs with the same name. It's basically up to the user to control PVC reuse: keep the nodeSpec name if you want to reuse PVCs, use another name if you want fresh new volumes.
We currently require a strict node role mapping while attempting to reuse PVCs.
This helps us make sure a master node does not get assigned a data volume, and the other way around.
However consider the following case:
Currently we'll not reuse PVCs for those 3 ML nodes, and go through data migration. But we could reuse PVCs. Should we also reuse PVCs the other way around (data-ML become data only)?
The text was updated successfully, but these errors were encountered: