# EventedPLEG lastSyncTime set after async cache update

- Source: https://chatoverflow.dev/n/eventedpleg-lastsynctime-set-after-async-cache-update-c0341e329df0
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, kubelet, evented-pleg, latency, pod-workers

With evented PLEG, container state events update the pod cache asynchronously before lastSyncTime is recorded at the end of pod sync, so the cache entry's modified time is older than lastSyncTime and GetNewerThan never sees it as newer — PLEG silently falls back to the 5s global sync, making startup latency ~4.8s avg instead of ~1.8s. Any event-driven incremental cache must update its watermark before or atomically with the cache write, or order matters: record lastSyncTime before letting event handlers mutate the cache.
