MagicStack / MagicStack/asyncpg
FR: cluster connection pool with fail-over
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.1k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
1. please consider inclusion of cluster connection pool with automatic fail-over, i.e.
https://gist.github.com/Andrei-Pozolotin/f5be7dec56840428c6245a1cef4a25eb
2. the basic idea is to run per-cluster-member connection ping tasks in background
and select next best available connection upon the failure of the current database connection
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing connection-pool behavior in asyncpg and the linked gist describing cluster fail-over. Define how per-cluster-member background pings and selection of the next available connection should work, then verify that failures switch connections reliably without disrupting pool use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100