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
We recently added the ability to configure the pool_size and max_overflow on Sqlalchemy engines created ops-side, but the ctl side also has engines that are not yet configurable.
The consequences of having low limits here is that users can hit QueuePool errors when there are a small number of simultaneous connections on the database.
Describe the solution you'd like
Ideally, we'd consolidate some of the ctl and ops engines (ctl side also has asynchronous engines) while we're at it too. A quick change would be just making the ctl engines configurable.
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a specific problem?
Related comment: #2511
We recently added the ability to configure the pool_size and max_overflow on Sqlalchemy engines created ops-side, but the ctl side also has engines that are not yet configurable.
The consequences of having low limits here is that users can hit QueuePool errors when there are a small number of simultaneous connections on the database.
Describe the solution you'd like
Ideally, we'd consolidate some of the ctl and ops engines (ctl side also has asynchronous engines) while we're at it too. A quick change would be just making the ctl engines configurable.
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: