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
When a DB replica is offline for maintenance, frontend instances bound to that replica fail all requests, resulting in a high request failure rate across the frontend pool.
Cause:
Frontend instances randomize their primary DB host choice at startup.
The current fallback mechanism to the secondary DB host is only executed during startup connection check.
Once running, the connection pool remains static and cannot route around the dead replica.
Potential solution to look into:
The driver supports multi-host DSN. Configure connection strings with all the replica hosts.
Configure the connect timeout in the DSN, so connection attempts to an offline host time out quickly and fail over to the healthy one.
When a DB replica is offline for maintenance, frontend instances bound to that replica fail all requests, resulting in a high request failure rate across the frontend pool.
Cause:
Potential solution to look into:
The driver supports multi-host DSN. Configure connection strings with all the replica hosts.
Configure the connect timeout in the DSN, so connection attempts to an offline host time out quickly and fail over to the healthy one.