Dynamic backups
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 470
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
As described already in discussion section it may for various reasons (work around to allow scale down while maintaining HA, mirror typical HA setup of cloud providers with 3 AZs, speed up get&getAll requests in 3 AZ cloud setups) be interesting to have backup count of 2 but in the event of an AZ failure it would be desirable to abandon the second backup to conserve memory.
Contributor guide
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 discussion section referenced in the issue and reading the existing backup and availability behavior for availability-zone failures. Define how a configured backup count of two should change after an AZ failure, including memory conservation and continued high availability, then identify the relevant implementation and tests before proposing the design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cloud, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100