fix(shutdown): kill server after timeout when hanging on shutdown
When socket.io is not able to close a connection somehow, the code never reaches the final shutdown state but keeps waiting for all connections to be closed. This can cause a high CPU load on failing shutdown. It is very unlikely to happen, except when the server is shut down exactly at the same time a socket is disconnecting and not already marked as disconnected. This change adds a fallback timer which forcefully kills the server after a certain amount of time. Signed-off-by: Erik Michelson <github@erik.michelson.eu>
This commit is contained in:
@@ -12,7 +12,8 @@
|
||||
|
||||
### Bugfixes
|
||||
- Ignore the healthcheck endpoint in the "too busy" limiter
|
||||
- Send the referrer origin for YouTube embeddings due to their requirement
|
||||
- Send the referrer origin for YouTube embeddings due to their requirement
|
||||
- Force kill the server after a timeout when waiting for the realtime server to close connections on shutdown
|
||||
|
||||
## <i class="fa fa-tag"></i> 1.10.3 <i class="fa fa-calendar-o"></i> 2025-04-09
|
||||
|
||||
|
||||
Reference in New Issue
Block a user