MapColonies / MapColonies/geocoding
Retry mechanism for Redis connection (MAPCO-4891)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Currently Redis tries to connect once, and if it doesn't work it gives up.
Before, if Redis didn't connect, then the application didn't start.
Expected behavior
The connection of Redis shouldn't affect the application. Redis should try reconnecting every specified amount of time.
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 locating the Redis connection setup and reviewing how a failed initial connection is handled. Check whether the project already exposes a retry interval, then determine how startup behaves when Redis is unavailable. Done means the application can start without Redis and the connection retries at the specified interval.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- redis, typescript
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100