https://minuk.dev/opampcommander/docs/deployment/Recent content in Deployment on OpAMP CommanderHugoen-ushttps://minuk.dev/opampcommander/docs/deployment/kafka-degradation/Mon, 01 Jan 0001 00:00:00 +0000https://minuk.dev/opampcommander/docs/deployment/kafka-degradation/<p>Kafka events are best-effort notifications of state already saved in the database. An API success confirms persistence, not broker delivery or an agent acknowledgement. The same-node event path dispatches directly to local connections without Kafka.</p> <p>For remote agents, notifications normally prompt an immediate push. If a notification or cache invalidation is lost, subsequent OpAMP heartbeats reload persisted state once the agent cache expires (30s by default). Cache reads do not extend that TTL. Recovery therefore depends on the database remaining available and the agent sending another message; it does not require Kafka to reconnect. Later updates may supersede older desired state. This is state convergence, not an ordered replay of every command or an exactly-once execution guarantee. Previously stored restart requests can now be offered after a reload if the reported agent start time precedes the request; a newer reported start time suppresses the command.</p>