-
Notifications
You must be signed in to change notification settings - Fork 21
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
Healthcheck could break update #59
Comments
Oh, yeah that's a good point. That sounds like a good idea too. Having some kind of health check script which takes into account that a potential upgrade might be in progress. We could probably use some kind of placeholder file (ie Want to throw together a PR with a script to get this all working ok? 😄 |
i can look into it the next days :) |
Merged that PR. Lets see how it goes in actual use. 😄 |
had an upgrade from 14 to 17 on a friends db without problems. also my dbs are running fine. lets see what the next major release will do :) dont have any old db to test atm |
Yeah. It passes all of the automated testing too, so the main upgrade functionality is ok at a minimum. 😉 |
if I have one input: I could imagine that a couple of folks keep their standard healthcheck with |
That's a decent idea. Anyone feel like writing it? 😄 |
i think another one for me :P |
A wild volunteer appears! 😁 |
done |
i run this image in a swarm cluster that checks for health and if the container is unhealthy it restarts the container and try to get it running. this will happn in the upgrade process which dont work.
i used
i think nothing we can do about directly (maybee providing a script that does this healthcheck but will also exit code 0 when an update is running?) but more a think we should mention?
The text was updated successfully, but these errors were encountered: