We need mechanism for delayed_job to respond to SIGQUIT the same way it currently responds to SIGTERM due to disagreements between the rails and nginx about which should be triggering graceful shutdowns.
As of now delayed job containers terminate abruptly on SIGQUIT leaving jobs in a half done state.
We need mechanism for delayed_job to respond to SIGQUIT the same way it currently responds to SIGTERM due to disagreements between the rails and nginx about which should be triggering graceful shutdowns.
As of now delayed job containers terminate abruptly on SIGQUIT leaving jobs in a half done state.