Telemetry: evict a driver's snapshot-cache entries when the instance is removed #609
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
_healthCache/_resilienceCacheare never evicted, so a decommissioned driver instance's last Health/Resilience is replayed to every new/hostssubscriber forever ("pre-production, accepted for now").Sources: src/Server/ZB.MOM.WW.OtOpcUa.Runtime/Telemetry/TelemetryLocalHub.cs:40-42 (
TODO(mesh-phase5+)); deferment.md §4.1.Filed 2026-10-08 by the pending/deferred-work sweep after the #562–#591 issue sweep.
Resolved on master (
53247a05merge 93e38156;8a9bf230in merge b99aea46;4a10ea1emergeb9e6802d).TelemetryLocalHub,ITelemetryLocalHub); the removed driver's resilience tracker state is released as well so the publisher stops re-emitting it.TelemetryLocalHubTests,DriverHostActorUnreadableArtifactTests).4a10ea1e: a removed driver's late in-flight invoker calls or health emits can no longer resurrect that state (tombstones on the tracker and hub, Retire/Reinstate, Evict/Readmit). The tombstone note is in CLAUDE.md. The TODO(mesh-phase5+) is gone.Closed 2026-10-08 by the hardware-available issue sweep (master
d898262c).