Jump to content

Connect SuperML | Leeroopedia MCP: Equip your AI agents with best practices, code verification, and debugging knowledge. Powered by Leeroo — building Organizational Superintelligence. Contact us at founders@leeroo.com.

Principle:LMCache LMCache Worker Registration

From Leeroopedia
Revision as of 18:21, 16 February 2026 by Admin (talk | contribs) (Auto-imported from principles/LMCache_LMCache_Worker_Registration.md)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Knowledge Sources
Domains Distributed_Systems, Service_Discovery
Last Updated 2026-02-09 00:00 GMT

Overview

A registration and heartbeat pattern where LMCache worker agents register with a centralized controller and maintain liveness through periodic heartbeats.

Description

Worker Registration is the process by which each LMCache-enabled vLLM instance announces itself to the centralized controller. An LMCacheWorker agent is created alongside the cache engine, connects to the controller's ZMQ endpoints, sends a registration message with instance metadata (instance_id, worker_id, NIXL host/ports), and starts a heartbeat loop that periodically sends cache statistics.

Usage

Worker registration happens automatically when enable_controller=True in the config. The worker agent is created by LMCacheManager during initialization.

Theoretical Basis

Registration follows a register-heartbeat-deregister lifecycle:

  1. Register: Worker sends instance metadata to controller via ZMQ REQ
  2. Heartbeat: Worker periodically sends cache statistics via ZMQ PUSH
  3. Timeout: Controller marks worker as dead if heartbeat stops for lmcache_worker_timeout seconds

Related Pages

Implemented By

Page Connections

Double-click a node to navigate. Hold to expand connections.
Principle
Implementation
Heuristic
Environment