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
Describe the bug
It seems the services open a lot of connections towards the databases (~30), instead of a few by service (~1-2). With all the services running in version 2.0 (broker, console, telemetry, ...) the total of connections towards the SQL database goes up to ~ 200.
To Reproduce
Simply launch the service while monitoring the connections in the database.
Expected behavior
It may be reasonable to have more than one connection open from a single service, but 30 by each seems too many. It makes harder to monitor properly the status of the database and the noise provoked by such quantity of connections does not help to detect possible attacks against the database for example.
Version of Kapua
2.0.0, but happens for a long time
Type of deployment
[X] Docker, with a MariaDB database
Main component affected
All SQL database related
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
It seems the services open a lot of connections towards the databases (~30), instead of a few by service (~1-2). With all the services running in version 2.0 (broker, console, telemetry, ...) the total of connections towards the SQL database goes up to ~ 200.
To Reproduce
Simply launch the service while monitoring the connections in the database.
Expected behavior
It may be reasonable to have more than one connection open from a single service, but 30 by each seems too many. It makes harder to monitor properly the status of the database and the noise provoked by such quantity of connections does not help to detect possible attacks against the database for example.
Version of Kapua
2.0.0, but happens for a long time
Type of deployment
[X] Docker, with a MariaDB database
Main component affected
All SQL database related
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: