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 Jan 5, 2022. It is now read-only.
Is there a specific reason why the influxdb chart uses a Deployment instead of a StatefulSet? If I understand correctly, this means that two pods will share the same PV for a short amount of time during pod reschedules (e.g. updates, node drains).
Is InfluxDB able to handle concurrent R/W access to data files from multiple instances? If so, a Deployment probably works fine. If not, this may be a serious possibility for data corruption and a StatefulSet would be the only right choice here.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there a specific reason why the
influxdb
chart uses a Deployment instead of a StatefulSet? If I understand correctly, this means that two pods will share the same PV for a short amount of time during pod reschedules (e.g. updates, node drains).Is InfluxDB able to handle concurrent R/W access to data files from multiple instances? If so, a Deployment probably works fine. If not, this may be a serious possibility for data corruption and a StatefulSet would be the only right choice here.
The text was updated successfully, but these errors were encountered: