-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Storage Execution 2026-09-28, Storage Execution 2026-10-12, Storage Execution 2026-11-23
-
None
-
None
-
None
-
None
-
None
-
None
-
None
- Have counters with cumulative invalidations and record why we invalidated with the time, including prepared transactions and missing contributions (tbh this should be a very rare event after we support prepared txn, so there aren't many use cases where we would have an absent hash).
- Distinguish absent hashes from unsupported collections vs. collections that should be supported but aren't.
- Matching size/count with absent hashes must not count as a successful content-hash comparison (make a metric for number of comparisons without a hash where a collection is eligible for a hash).
- Treat hash value zero as valid, not absent.
- depends on
-
SERVER-135658 Change disableContinuousInternodeValidation to still emit the hash
-
- Closed
-