-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines, Storage Engines - Foundations
-
SE Foundations - Q4+ Backlog
-
None
When running 'jstests/noPassthrough/query/yield/query_yields_catch_index_corruption.js', the following assertion will fail, not because we don't write the correct oplog entry, nor because we don't detect validation in this case, but rather, because when we run the[ following code in 'validate', |https://github.com/10gen/mongo/blob/79b60eb64de59ffeac209473299da7ada498f550/src/mongo/db/validate/index_consistency.cpp#L979-L983] the WT cursor returns WT_NOTFOUND. This in turn causes us not to report the timestamps corresponding to the oplog entries of the dangling writes and we fail to log the following message, causing the test to fail.
This ticket tracks the work to determine why opening this cursor doesn't work with DSC.