ES failover does not switch between options
Open
area: herald
type: bug
- Dominant language
- Python
- Stars
- 15
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
If two sets of ES services are defined herald will not try one after the other when the primary goes down, it will get stuck retrying the one it hadn't been connected to.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing Herald's ES service selection and retry behavior, then reproduce the failure with two defined service sets and the primary unavailable. Done means Herald attempts the alternate set instead of repeatedly retrying the set it could not connect to.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100