Bertrand Renuart

I understand, but before asking for changes in the documentation I think my analysis needs to be reviewed by someone with better understanding of Eureka's internals and make sure the...

Does that mean you feel as lonely as me? ;-)

Here is a first attempt to answer the question _"Why does it take so long to register an instance with Eureka?"_ Tell me if you think this kind of information...

Not much time for the moment but I'll try to extend coverage of "my" doc. Maybe I should coordinate with @spencergibb to incorporate those few lines into the official doc...

_self-preservation_ is a mechanism by which the Eureka registry stops expiring entries when it detects that an "important" amount of services didn't renew their lease in time. This should protect...

The issue is due to the following: - `EurekaDiscoveryClientConfiguration` implements `SmartLifeCycle` and is being closed first - it is also a `@EventListener(ContextClosedEvent.class)` that supposed to be invoked when the context...

Could be I missed something, but using an Eureka HealthCheckHandler is not required to support instances starting with a STARTING status then UP once fully started. We do have the...

As I said, the status will *always* come from the healthcheck if one is registered and returns a non-null value - otherwise the status from AppInfoManager is taken. The bottom...

Ribbon can indeed be configured to retry the same server a couple of times before trying the next one. If the server replies with SERVER_THROTTLED, there is no point in...

It is indeed a Netflix/Ribbon specific feature that is hardcoded in their RestClient. The client returns `ClientException.ErrorType.SERVER_THROTTLED` when it gets a `503 (Service Unavailable)` from the downstream server. When `okToRetryOnAllErrors`...