-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
Storage Execution 2026-11-09
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Problem
Since SERVER-133545, the primary marks the collection dropped by renameCollection with dropTarget as removed in its replicated
metadata checkpoint. The standby's checkpoint validator (SERVER-136545) does not record a delta for rename entries. When it validates a
checkpoint covering such a rename, it does not expect the target to be removed and fasserts:
Fatal assertion 13626002: Replicated metadata checkpoint is missing collection <target uuid> which the standby did not observe as dropped
This crashes any standby with enableContinuousInternodePerCollectionValidation enabled once a renameCollection with dropTarget is replicated.
Cause
- Primary: processOplogEntry in replicated_fast_count_delta_utils.cpp handles kRenameCollection by recording a dropped delta for
the dropTarget UUID. - Standby: recordDdlDelta in repl/oplog.cpp only handles kCreate and kDrop. Its default: comment says the primary does
not use the other commands for its checkpoint, which stopped being true withSERVER-133545.
- is depended on by
-
SERVER-136296 Enable standby collection validation fassert server parameter
-
- In Progress
-