spring-cloud / spring-cloud/spring-cloud-netflix
Add retry support for non-jersey eureka client
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 5k
- Forks
- 2.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 10
Description
Version: Hoxton.SR5
I have two eureka servers configured in application's bootstrap.yml, but only the first is used when application is trying to bootstrap. When the first eureka server is down, application cannot start.
eureka:
client:
serviceUrl:
defaultZone: http://uat4-eureka:8761/eureka,http://uat5-eureka:8761/eureka
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
The issue names only the bootstrap.yml Eureka configuration and does not identify repository files or tests. Start by locating the non-Jersey Eureka client startup path and its handling of multiple serviceUrl entries; done should mean the client can start when the first configured Eureka server is unavailable and has coverage for that scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100