Retry mechanism for Redis connection (MAPCO-4891)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- redis, typescript
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.
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.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from MapColonies/geocoding
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MapColonies/geocoding#54 ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 25/100
MapColonies/geocoding#47 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
MapColonies/geocoding#44 ·
-
Refactor
Difficulty 3/5 1-2 days Newbie friendliness 48/100
MapColonies/geocoding#43 ·
-
bug In Design
Difficulty 5/5 Over a week Newbie friendliness 25/100
MapColonies/geocoding#28 ·
All issues in MapColonies/geocoding
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100