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
I know that with consul we have fault tolerance, but there maybe a possibility where all my consul servers are going down together. Then in that scenario, I will loose all the configuration I have stored in the K/V store.
Does the -v /mnt:/data also gives persistence to the data in my K/V store?
The text was updated successfully, but these errors were encountered:
As you know, consul can get into a broken state when servers are not restarted in a rolling fashion. This is the behavior of consul itself, and not particular to this image, so in performing outage recovery, consult the guide at https://www.consul.io/docs/guides/outage.html
The google groups thread I linked above includes some comments/recommendations on the topic of backing up the K/V store, and when this is relevant/recommended.
In any case, the immediate answer is: yes, your K/V data is persisted in the data directory, so if you would like it to be persistent across several containers, use a shared volume of some sort.
I know that with consul we have fault tolerance, but there maybe a possibility where all my consul servers are going down together. Then in that scenario, I will loose all the configuration I have stored in the K/V store.
Does the -v /mnt:/data also gives persistence to the data in my K/V store?
The text was updated successfully, but these errors were encountered: