lease expiration on standalone Eureka server with self-presenvation enabled is broken

[ViliusS]

It looks like lease expiration on standalone Eureka server with self-presenvation enabled is completely broken. I have the following configuration:

eureka.instance.hostname=localhost
eureka.client.serviceUrl.defaultZone=http://localhost:8761/eureka/
eureka.client.register-with-eureka=false
eureka.client.fetch-registry=false
eureka.server.renewalThresholdUpdateIntervalMs=60000
# this should be the same as eureka.instance.lease-renewal-interval-in-seconds on the clients
eureka.server.expected-client-renewal-interval-seconds=10

If I start completely empty server with this configuration it says:

c.n.e.r.PeerAwareInstanceRegistryImpl    : Got 1 instances from neighboring DS node
c.n.e.r.PeerAwareInstanceRegistryImpl    : Renew threshold is: 5

I tracked it down to defaultOpenForTrafficCount which by default is set to 1, changed to
eureka.instance.registry.defaultOpenForTrafficCount=0 . Now the server starts with:

c.n.e.r.PeerAwareInstanceRegistryImpl    : Got 0 instances from neighboring DS node
c.n.e.r.PeerAwareInstanceRegistryImpl    : Renew threshold is: 0

Issue however not solved because even if I add dozen of eureka clients the threshold never changes even when is actually recalculated. I get c.n.e.r.PeerAwareInstanceRegistryImpl : Current renewal threshold is : 0 in the logs every minute.

Hence, lease expiration never kicks in unless I completely disable self-preservation mode.

[ViliusS]

To add on top of that, looks like expectedNumberOfClientsSendingRenews is never passed to Eureka and is always calculated by Eureka itself automatically.

[OlgaMaciaszek]

Hello @ViliusS , please provide a minimal, complete, verifiable example that reproduces the issue.

[ViliusS]

Here you go
eureka.zip

Just run this Maven project which should start Eureka server in standalone mode. After that, connect any number of Eureka clients to it. In the logs you will always see: c.n.e.r.PeerAwareInstanceRegistryImpl : Current renewal threshold is : 0.

This doesn't allow leases to expire, unless you disable self preservation mode.

[OlgaMaciaszek]

For defaultOpenForTrafficCount the javadoc sais "Should be set to 0 for peer replicated eurekas". For non-peer-replicated eurekas it should be one. Why are you setting it to 0 for testing with one server instance?

[OlgaMaciaszek]

I have changed the value referenced above back to 0 and return the sample. Also, the value of expectedNumberOfClientsSendingRenews is passed initially while creating the registry, that is modified by the openForTraffic() method call. The javadoc for that method sais: "If PeerAwareInstanceRegistryImpl#openForTraffic(ApplicationInfoManager, int) is called with a zero argument, it means that leases are not automatically cancelled if the instance hasn't sent any renewals recently. This happens for a standalone server. It seems like a bad default, so we set it to the smallest non-zero value we can, so that any instances that subsequently register can bump up the threshold."
Since we're running a standalone server here, it seems to behave as documented.

[OlgaMaciaszek]

However, after I've run a client against the updated sample, when register is called, the value I set in expectedNumberOfClientsSendingRenews + 1 is being used to set the value of expectedNumberOfClientsSendingRenews before calling updateRenewsPerMinThreshold(), so that also behaves as expected.

[ViliusS]

defaultOpenForTrafficCount other than zero doesn't work if I change expected-client-renewal-interval-seconds to let's say 15 or 10 seconds. In such case, renewal threshold is always much higher than it should be for the lease expiration to work correctly.

So, maybe defaultOpenForTrafficCount is good for standard settings, but math definitely breaks somewhere with custom settings.

Btw, I don't understand why defaultOpenForTrafficCount javadoc says that it should be 1 for standalone eurekas. If standalone replica doesn't have any peers and if eureka.client.register-with-eureka=false and eureka.client.fetch-registry=false, like it should be for non-replica case, then it means Eureka doesn't have any clients during startup, does it?