Package com.kingsrook.qqq.backend.core.cluster
package com.kingsrook.qqq.backend.core.cluster
-
ClassDescriptionCluster control events (spec 2026-10-15-cluster-ha-design): when a node changes something other nodes hold in memory - a session ends, the meta data overlay changes, a cached record is edited - it publishes an event.Transport for cluster control events. publish sends to every node (possibly including this one - ClusterBus drops its own echoes); subscribe receives the events any node published.Which transport carries cluster control events (ClusterBus).Test helper: finds static Memoization fields that did not register with ClusterCaches (shared or node-local), so a new static cache cannot silently go stale on other nodes.The registry of in-memory caches (static Memoizations and the like).A control event sent to every node of a cluster (ClusterBus): something a node changed that the other nodes hold in memory.A single-node cluster bus: events never leave this JVM.This node's lifecycle in a cluster: a node that is draining reports not-ready (so the load balancer stops sending it requests), stops claiming new work, and lets in-flight work finish before it stops (spec section D).What this node of a multi-node application does (docs/specs/ 2026-10-15-cluster-ha-design.md, section A).A node role.The resolved settings of this node.