spring-cloud / spring-cloud/spring-cloud-netflix
Eureka Clustering documentation and best practices
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5k
- Forks
- 2.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 10
Description
I understand that there is a section in the documentation about Eureka Peer Awareness, but somehow I do not find this enough.
I find it hard to understand how this would make Eureka more HA. There would be a chain server1, server2, server3 and they are cross referenced, but if one node fails the chain breaks anyway.
Would it be a good option to just specify a list containing all 3 servers separated by comma for each all of them (server1, server2, server3)?
What is your experience?
PS: did not try DNS yet
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 reviewing the existing Eureka Peer Awareness documentation and the 28-comment discussion on this issue. Compare the documented clustering and DNS options with the questions raised, then define the documentation changes needed to explain the HA topology and recommended configurations; done means the guidance addresses the failure scenario clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100