Lease or Heartbeat Registration¶
Liveness protocol — instantiates Registry-Mediated Discovery
Lets a provider publish its current locator under a time-bounded lease it must keep renewing; if the heartbeat stops, the entry auto-expires, so the registry only ever advertises things that are still alive.
Lease or Heartbeat Registration is the provider-side mechanism that keeps a registry honest about liveness. An entity registers itself and its current locator, but the registration is not permanent — it comes with a lease that expires unless the provider proves it is still there by renewing, or by sending periodic heartbeats. What makes it this mechanism is that presence is self-asserted and self-expiring: nothing removes a dead entry by hand; it simply ages out when the heartbeats stop. The registry's freshness is therefore a property of who keeps talking, not of who last got audited. A caller reading the registry can trust that a listed locator was alive within one lease interval.
Example¶
A laptop joins an office network and needs an IP address. It broadcasts a DHCP request; the DHCP server offers an address on a lease — say four hours — and records the binding of that address to the laptop's hardware identifier. The lease is not forever: at the halfway point the laptop tries to renew, and if it does, the binding stays current. But if the laptop is shut down and carried home, the renewals stop; when the lease expires, the server reclaims the address and the binding disappears, free to be reassigned. No administrator deletes anything. The registry of who-currently-holds-which-address stays accurate purely because holders must keep renewing to stay listed, and silence is read — correctly — as departure. The locator record (address bound to device, with a lease clock) is exactly what makes reclamation safe.
How it works¶
A provider registers a record — its current locator plus whatever the schema requires — and receives a lease with a time-to-live. To stay listed it must renew before the TTL elapses, typically via lightweight periodic heartbeats that double as a coarse liveness signal. Missed renewals past a grace margin cause the registry to expire the entry automatically. The design's whole point is failure by omission: a crashed or partitioned provider cannot send a "goodbye," so the only robust signal of departure is the absence of expected heartbeats. Tuning the TTL and grace window trades detection speed against tolerance for transient blips. This is soft-state discovery — registry entries decay unless continuously refreshed — which is what lets the system self-heal without a reaper process hunting for corpses.[n1]
Tuning parameters¶
- Lease TTL — how long a registration survives without renewal. Short leases detect death fast but flood the registry with renewal traffic; long leases are quiet but advertise dead entries longer.
- Heartbeat interval — how often the provider checks in. Frequent heartbeats sharpen liveness at a bandwidth cost.
- Grace / miss threshold — how many missed beats before expiry. A wider grace tolerates transient network blips but slows removal of the genuinely dead.
- Renewal backoff — how a provider retries a failed renewal. Aggressive retry defends against flapping; gentle retry avoids storms during congestion.
- Health payload richness — whether heartbeats carry just "alive" or also load and readiness. Richer signals aid consumers but couple registration to internal state.
When it helps, and when it misleads¶
It is the right mechanism wherever membership is volatile and self-managing — instances that come and go, addresses that recycle, agents that crash without warning. It keeps a registry current with no manual gardening and degrades gracefully. Its failure mode is misreading the why of silence: a network partition looks identical to death, so a provider that is perfectly alive but briefly unreachable gets expired and its entry evicted — exactly when a flood of reconnections can then stampede. The classic misuse is setting the TTL so tight that ordinary latency triggers false expiries, thrashing the registry. The guarding discipline is to size the grace window against real network variance, not the happy path, and to distinguish "missed a beat" from "confirmed gone" before taking destructive action.
How it implements the components¶
freshness_and_liveness_policy— its defining contribution: the lease/TTL and renewal rules are the liveness policy, expiring stale presence automatically.health_signal— heartbeats double as a periodic liveness signal, optionally carrying load or readiness.locator_record_schema— each registration publishes the provider's current locator in the record shape the registry expects.
It does not decide, among the live entries, which one a caller should prefer — that ranking via routing_preference_metadata belongs to Service Registry — and it does not memoize a resolved answer on the caller under a resolver_cache_policy, which is Resolver Cache with TTL; a lease governs whether a provider stays listed, not how consumers choose or cache among the listings.
Related¶
- Instantiates: Registry-Mediated Discovery — the provider-side liveness protocol that keeps registry entries honest by self-expiry.
- Sibling mechanisms: Service Registry · Resolver Cache with TTL · Directory Service · Name Resolution Service · Registry Query API · Catalog or Broker Directory · Human Referral Directory · Federated Registry Synchronization · Successor Forwarding Record
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Lease or Heartbeat Registration operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it lets a provider publish its current locator under a time-bounded lease it must keep renewing; if the heartbeat stops, the entry auto-expires, so the registry only ever advertises things that are still alive
Independent corroboration: The frozen evidence defines Lease or Heartbeat Registration as 'Lets a provider publish its current locator under a time-bounded lease it must keep renewing; if the heartbeat stops, the entry auto-expires, so the registry only ever advertises things that are still alive', so its operative form is Control, Automation & Runtime.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Computer Science & Software Engineering
Origin pattern: Single lineage
Present-day reach: Specialized
Rationale: Distributed service-discovery systems developed lease-based registration refreshed by heartbeat so stale providers disappear automatically.
Review outcome: Independent reviewer agreement; high confidence.
Notes¶
Lease renewal and a caller-side cache TTL both count down a clock, which invites conflation — but they sit on opposite ends of the discovery path. This mechanism's clock governs whether a provider remains advertised; Resolver Cache with TTL's clock governs how long a consumer trusts an answer it already fetched. Keeping the two clocks conceptually separate is what lets a system detect a dead provider quickly while still letting callers cache generously.
[n1] Soft state (David Clark's characterization of Internet protocol design) — registry state that must be periodically refreshed by its owner or it decays, rather than persisting until explicitly deleted. It makes a discovery system self-healing: dead entries disappear on their own instead of needing a reaper. ↩