Core NATS delivers at most once. While a node's connection is down the
client reconnects by itself and subscribes again, but whatever the
cluster published meanwhile never arrives, and the account, token,
role, domain and DAV caches only ever change on those events, so they
stayed stale until a restart; a missed registry change left the running
settings stale the same way.
The NATS backend now counts reconnections on a watch. The broadcast
subscriber drops every local cache and reloads the settings,
certificates and blocked addresses on each one, and after subscribing
again when its stream ended. The message caches check the change log
on every use and need nothing.
jcoffey-dev