spring-cloud / spring-cloud/spring-cloud-netflix
About RefreshScopeRefreshedEvent
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5k
- Forks
- 2.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 10
Description
I found that the propagation of any RefreshScopeRefreshedEvent event will cause Eureka to restart. I think this is unreasonable. The event object already contains the name of the configuration object refreshed. You should check whether this name belongs to you before restarting.
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 tracing where RefreshScopeRefreshedEvent is handled in the Eureka restart path; the issue does not name a file or test. Check how the event's configuration-object name is represented and determine the expected filtering behavior. Done means unrelated refresh events no longer restart Eureka while the relevant event still does.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100