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
Recently been investigating some possible shutdown issues with one of our service. Started by suspecting that k8s was killing the service before it had time to shutdown cleanly but after setting up a simple test application can see that it could be the shutdown_timeout expiring.
Recently been investigating some possible shutdown issues with one of our service. Started by suspecting that k8s was killing the service before it had time to shutdown cleanly but after setting up a simple test application can see that it could be the
shutdown_timeout
expiring.Example application here: https://gist.github.com/EddieWhi/9de3486bced26c818f2be97c20a8fa9f
After running the application, curling
/
then curling/shutdown
after a few seconds I get the following logs:Which is similar to what we're seeing in production... the logs just stop, nothing to indicate that the service was forcefully killed.
It would be very useful to know that a service was being forcefully terminated. Certainly would help me right now.
Naively, I was thinking of making a PR along the lines of this: master...EddieWhi:actix-net:add-log-on-graceful-shutdown-timeout but wonder if I'm missing something obvious first?
Any help much appreciated.
The text was updated successfully, but these errors were encountered: