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
So this may be a weird request, but I have a dilemma. I have an application that requires patched versions of Redis and Memcached, so at checkout the setup script builds both of them from source. Because of this, both Redis and Memcached are started with the rest of the process in the development Procfile.
Would it be possible when Overmind receives a Ctrl+C to stop a program (in this case Rails and Sidekiq) before stopping Redis and Memcached so that the programs can store their data properly before shutdown?
Sorry for such a weird request.
The text was updated successfully, but these errors were encountered:
Hey @lunaisnotaboy!
This feature requires rewriting too much stuff for such a niche feature. So I'd not add it right away but I'll keep this feature request open just in case I or somebody comes up with a good solution.
Just making a note that I'm running into this exact situation as well of needing a few processes that are reliant on by others to be gracefully stopped before the other processes. Not sure of a real solution at the point, I'll noodle on it a bit, but could definitely see the value in having some way to say "don't send the kill signal to process X until after process Y has fully shut down."
So this may be a weird request, but I have a dilemma. I have an application that requires patched versions of Redis and Memcached, so at checkout the setup script builds both of them from source. Because of this, both Redis and Memcached are started with the rest of the process in the development
Procfile
.Would it be possible when Overmind receives a
Ctrl+C
to stop a program (in this case Rails and Sidekiq) before stopping Redis and Memcached so that the programs can store their data properly before shutdown?Sorry for such a weird request.
The text was updated successfully, but these errors were encountered: