Why keepalive fire lost after twice ttl about etcd3 HOT 3 CLOSED

Sorry for the delayed response, on the initial read I read it that lost was fired twice.

It's fired immediately after twice the TTL because that's the time when we consider it 'gone forever'. Without this, we would only notify the caller that the lease is lost if the server tells us it is in response to a heartbeat. But if the server is down entirely, this might not ever end up happening, so eventually we'll bail out and tell the consumer that their lease probably is no longer valid.

from etcd3.

You misunderstood me. The key to my opinion is the word twice. I think that time setting to TTL+3s is enough, twice TTL is too long. Do you think?

from etcd3.

Oh. Maybe. TTL should be chosen by consumers based on network latency and load factors. In extreme cases this may naturally be multiple seconds. I think that basing the "give up" trigger based off of the TTL they chose is reasonable. In normal operations that's a code path which is never hit, I'd prefer to be conservative about when we choose to go that way.

from etcd3.