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
What happened:
The process of server shutdown is implemented here, but it does not seem to perform actually during the server shutdown.
This may because that the application is not correctly catching the SIGTERM signal when the server is shutting down.
One possible reason is that the SIGTERM signals do not reach the actual node process if the application is executed in the order npm start -> node index.js. Especially, this problem seems to happen mainly with dockerized application.
What happened:
The process of server shutdown is implemented here, but it does not seem to perform actually during the server shutdown.
This may because that the application is not correctly catching the
SIGTERM
signal when the server is shutting down.One possible reason is that the
SIGTERM
signals do not reach the actual node process if the application is executed in the ordernpm start -> node index.js
. Especially, this problem seems to happen mainly with dockerized application.Refer the link below:
What you expected to happen:
Node processes for each component properly catch
SIGTERM
signals and perform graceful shutdown.How to reproduce it:
Delete or restart screwdriver.cd components on kubernetes.
The text was updated successfully, but these errors were encountered: