spring-cloud / spring-cloud/spring-cloud-netflix
Bus refresh event kicks off all services from Eureka
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5k
- Forks
- 2.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 10
Description
I'm not sure it's bug or question and to which project it relates, but I've found this case trying spring cloud bus, so I decided to post here.
Problem is whenever refresh event is sent to bus all service stats to re-registering in Eureka since eureka discovery client is refresh-scoped.
For test I've used:
SB version: 2.1.1.RELEASE
Cloud version: Greenwich.RC2
Service name: frontend-service
Instance count: 2
So is there any workaround for this? Since I'm looking for automatic configuration refresh, but not willing to see my cluster to be down after this.
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
Reproduce the refresh event with Spring Boot 2.1.1.RELEASE, Spring Cloud Greenwich.RC2, a frontend-service with two instances, Spring Cloud Bus, and Eureka. Start by examining how the refresh-scoped Eureka discovery client responds, then determine whether configuration refresh can avoid re-registering all services or document a workable alternative.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- backend, cloud, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100