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
Etherpad ignores SIGTERM. It processes SIGINT signal. This potentially causes an unexpected loss of data or data corruption when used with Docker as PID 1 and makes the shutdown unnecessarily slow.
what actually happened: Graceful shutdown time times out and container (the nodeJS process) is shut down forcefully by SIGKILL. Outgoing database connections and incoming client connections can't be gracefully closed. Internal buffers might not be written to disk (don't know whether this is an issue here, not an Etherpad insider).
Shut down database connection and exit the node process
when SIGTERM is encountered. This is especially important
when nodejs is run as PID1, e.g. in a docker container.
Shutting down connections to clients (browsers) is beyond
this patche's scope.
Resolves#3265
Etherpad ignores
SIGTERM
. It processesSIGINT
signal. This potentially causes an unexpected loss of data or data corruption when used with Docker as PID 1 and makes the shutdown unnecessarily slow.docker stop etherpad
C.f.
The text was updated successfully, but these errors were encountered: