spring-cloud / spring-cloud/spring-cloud-netflix
Documentation: changing Eureka renewal frequency *WILL* break the self-preservation feature of the server
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5k
- Forks
- 2.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 10
Description
In section "Why is it slow to register a Service?" of the documentation, it is said one can speed-up the client registration process by changing the heartbeat interval to a higher frequency (default is 30seconds).
The documentation also says it might not be a good idea in production without giving much explanations on the consequences.
One should be aware the self-preservation feature of the Eureka server makes the assumption clients are sending their heartbeat every 30 seconds - and this is not configurable. Using a different value will therefore break that functionality. It is definitely not a good idea to play with that parameter...
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
Find the documentation section titled "Why is it slow to register a Service?" and review its advice about changing the heartbeat interval. Update the explanation to state that Eureka self-preservation assumes 30-second client heartbeats and that changing the interval can break this feature; confirm the warning accurately reflects the reported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100