-
Notifications
You must be signed in to change notification settings - Fork 68
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
Metadata about snapshots destroyed when Consul is destroyed #36
Comments
We write a key to Consul to let the |
Is there a way to have the Consul instance write it's key/value pairs to a persistent storage area? Could the manage.py script look into Manta to find the latest backup if Consul doesn't know? |
That would be a function of how and where you deploy Consul. In an environment with attached network volumes (ex. NFS or soon-to-be-released Joyent/RFD26-style volumes) I imagine you could have your Consul containers use that. A better approach is to have a Consul raft for HA and then the failure of individual nodes won't delete data.
Sure, in theory, but none of our locks can work without Consul. But maybe I'm not understanding the problem you're running into. If you blow away all the metadata for orchestration then none of your service discovery works. I think the right way to fix that is to not blow it away and make sure it's HA. |
Sorry for the late reply, I was on vacation... My concern is that if (for whatever reason) all of the Consul instances in HA somehow die, none of the metadata will be available when the environment is repaired. The databases will come backup fresh and clean, and all of the data previously stored is "lost". The last backups would stil exist, but the DB servers would not go and fetch them to restore. Are there examples for Consul using a network volume to store the metadata persistently (e.g., into Manta)? |
Manta isn't a block store so it wouldn't be suitable except for backups. You're probably looking for NFS or soon-to-be-released Joyent/RFD26-style volumes. Alternately, you could add ContainerPilot to your Consul instances and give it a |
Ok, so this is really a "how do I backup Consul?" question at this point, so if there aren't any objections I'm going to close it. Feel free to reopen if there's more to discuss @headw01 |
When I bring an entire environment up (and down and up), should the database snapshot from the previous time (which is stored in Manta) be used?
It seems that the Consul state isn't maintained anywhere persistently, so the next time the environment comes up, it starts fresh.
If I scale the mysql service after the environment is up, it does get the snapshot from Manta...
First MySQL service startup (after many other "docker-compose up -d")
The text was updated successfully, but these errors were encountered: