Failover without fail recovery
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
We have a stateful app that is running on two VMs:
VM1 ( /usr/local/bin/lelastic -dcid XX -primary &)
VM2 (/usr/local/bin/lelastic -dcid XX -secondary &)
When VM1 is down, the elastic IP is moved to VM2 and that is a session interruption for customers, but that's OK.
Once VM1 is up, the elastic IP is moved back to VM1 and that's another session interruption for customers.
Is this possible to run lelastic in some way (both with -primary flag?) that prevent fail recovery mechanism?
If the IP is failed back to VM2, lets it running from VM2 until tthe VM2 is up, even VM1 become online as well?
Thank you.
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
No source files or tests are named. Start by tracing how the /usr/local/bin/lelastic -primary and -secondary modes handle failover when VM1 returns; done means confirming whether failback can be prevented so VM2 retains the elastic IP until it is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100