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
SudoSOS saturates all its available MariaDB connections and does not close any connections it is not using. This is problematic, as it is for example not possible to use the CLI. Also, when restarting, it might be that all connections are in use and the rebooted instance is not able to make any DB connections, thus not starting properly.
Desired behavior
Possible solutions might be:
Gracefully close all connections when stopping SudoSOS (AppDataSource.destroy()).
Do not keep any connections alive; instead, have TypeORM make a new connection for every query/transaction.
However, other (undiscovered) possible solutions might also work.
API Route
No response
Steps to reproduce
Start SudoSOS prod on the GEWIS server. If you try to use the CLI, it will not have any connections available. Furthermore, a restart might cause it to hang on [INFO] Application - Starting application instance....
Logs and Error Messages
No response
Other Information
No response
The text was updated successfully, but these errors were encountered:
Current behavior
SudoSOS saturates all its available MariaDB connections and does not close any connections it is not using. This is problematic, as it is for example not possible to use the CLI. Also, when restarting, it might be that all connections are in use and the rebooted instance is not able to make any DB connections, thus not starting properly.
Desired behavior
Possible solutions might be:
AppDataSource.destroy()
).However, other (undiscovered) possible solutions might also work.
API Route
No response
Steps to reproduce
Start SudoSOS prod on the GEWIS server. If you try to use the CLI, it will not have any connections available. Furthermore, a restart might cause it to hang on
[INFO] Application - Starting application instance...
.Logs and Error Messages
No response
Other Information
No response
The text was updated successfully, but these errors were encountered: