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
Currently, many parameters of the MySQL backend connection pool used by Gravitino, such as maxConnectCount and maxIdleConnect, are not configurable, and no relevant monitoring is configured for this connection pool. However, in reality, nearly every Gravitino REST request involves a call to the backend storage. Therefore, I believe it is essential to configure connection pool monitoring for a backend storage like MySQL in a production environment.
How should we improve?
We have configured monitoring for the MySQL backend in production. You can assign this to me, and I will complete it.
The text was updated successfully, but these errors were encountered:
TEOTEO520
changed the title
[Improvement] Provide Gravitino MySQL Backend Storage Connect Pool
[Improvement] Provide Metrics for Gravitino MySQL Backend Storage Connect Pool
Nov 14, 2024
TEOTEO520
changed the title
[Improvement] Provide Metrics for Gravitino MySQL Backend Storage Connect Pool
[Improvement] Provide Metrics for Gravitino MySQL Backend Storage Connect Pool
Nov 14, 2024
It's a useful feature, maybe we can report the connection pool metrics to the prometheus (already used by the API metrics). By the way, from my current feeling, this feature requires multiple PRs to complete, maybe you can list the sub tasks firstly.
What would you like to be improved?
Currently, many parameters of the MySQL backend connection pool used by Gravitino, such as maxConnectCount and maxIdleConnect, are not configurable, and no relevant monitoring is configured for this connection pool. However, in reality, nearly every Gravitino REST request involves a call to the backend storage. Therefore, I believe it is essential to configure connection pool monitoring for a backend storage like MySQL in a production environment.
How should we improve?
We have configured monitoring for the MySQL backend in production. You can assign this to me, and I will complete it.
The text was updated successfully, but these errors were encountered: