You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(lifecycle): debounce bucket processor scan-end to prevent false idle signals
The drain callback on _internalTaskScheduler fires every time the
queue goes from non-empty to empty. Under light load this happens
between Kafka message batches within the same conductor scan,
prematurely resetting the scan start time gauge to 0 and setting
_processorScanMetricsActive to false.
Because subsequent messages carry the same conductorScanId, the
new-scan branch is skipped and onBucketProcessorScanStart is never
called again, leaving the Bucket Processor Scan Progress dashboard
panel hidden for the remainder of the scan.
Fix: replace the immediate reset with a 30-second debounced timeout.
If new messages from the same scan arrive during the debounce window
the timeout is cancelled, keeping the scan active. A new scan also
cancels any pending debounce before performing a full metric reset.
Issue: BB-740
0 commit comments