Improve connection_pool connection retry strategy
- Dominant language
- C++
- Stars
- 299
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
* The retry strategy is currently very simple (linear time between retries) and not configurable. When there are a lot of connections, this can saturate the network. A configurable retry strategy may be an option. An exponential backoff may be beneficial.
* When `initial_size` is big, all connections attempt an establishment try at the same time. This can again cause congestion. We may want to limit this.
* This may also cause trouble with https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_max_connect_errors
Contributor guide
No contributing guide indexed for this repository
Research direction
No source files or tests are named. Start by locating the connection_pool implementation and its connection-establishment and retry entry points, then review how initial_size launches attempts; done means a configurable retry strategy and controlled startup behavior that avoids the described congestion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, mysql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100