-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
Storage Execution 2026-10-26
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In StreamingOplogDeltaAccumulator, the fast-lane handling of a malformed/missing ts field is inconsistent across the FastDecision cases. The kCrud, kCommitTxn, and kApplyOps lanes only guard whether lastTimestamp is advanced, but still return unconditionally. Meanwhile, the kCountedNoDelta lane breaks to Layer 3 on a non-timestamp ts.
In the unguarded cases, an entry with a malformed ts can be treated as "processed" and never falls through to Layer 3. For example, this happens on any tryRecordFastCrud path that returns 0, such as when 'm' is absent.
We should consider hoisting the ts validity check or otherwise applying it consistently if it is possible for entries with a corrupt ts to reach the fast lane.