spring-cloud / spring-cloud/spring-cloud-netflix
eureka client down after invoke refreshScope.refreshAll() ?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5k
- Forks
- 2.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 10
Description
The service of the eureka client is offline after using refreshAll or refresh(beanName).
My troubleshooting conclusion is that executing the refreshAll() or refresh(beanName) method will trigger multiple StatusChangeEvents and call the instance. setStatus() method in parallel to modify the instance status.
My idea is to disable eureka refresh, but after turning off the configuration, the application can still receive the RefreshScopeRefreshedEvent event.
So are there two things to consider?
1）If I set the configuration refresh to false: eureka.client.refresh.enable=false，then EurekaClientConfigurationRefresher should not receive the RefreshScopeRefreshedEvent event
2）If EurekaClientConfigurationRefresher receives the RefreshScopeRefreshedEvent event, it should do a layer of filtering, such as whether the event name is 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
Start by reading EurekaClientConfigurationRefresher and tracing how RefreshScopeRefreshedEvent is handled after refreshAll() or refresh(beanName). Verify the behavior when eureka.client.refresh.enable=false and determine whether Eureka-related events need filtering; done means refresh no longer takes the Eureka client offline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100