-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
Blocker - P1
-
None
-
Affects Version/s: None
-
Component/s: None
This issue has been detected through MongoDB's CI.
Validation on the collection test.coll on the secondary resulted in detecting an incorrect key sorting for an index:
[js_test:clean_shutdown_oplog_state] Collection validation failed on host localhost:21021 with response: {
[js_test:clean_shutdown_oplog_state] "ns" : "test.coll",
[js_test:clean_shutdown_oplog_state] "nIndexes" : 0,
[js_test:clean_shutdown_oplog_state] "keysPerIndex" : {
[js_test:clean_shutdown_oplog_state]
[js_test:clean_shutdown_oplog_state] },
[js_test:clean_shutdown_oplog_state] "indexDetails" : {
[js_test:clean_shutdown_oplog_state]
[js_test:clean_shutdown_oplog_state] },
[js_test:clean_shutdown_oplog_state] "valid" : false,
[js_test:clean_shutdown_oplog_state] "repaired" : false,
[js_test:clean_shutdown_oplog_state] "warnings" : [ ],
[js_test:clean_shutdown_oplog_state] "errors" : [ ],
[js_test:clean_shutdown_oplog_state] "extraIndexEntries" : [ ],
[js_test:clean_shutdown_oplog_state] "missingIndexEntries" : [ ],
[js_test:clean_shutdown_oplog_state] "corruptRecords" : [ ],
[js_test:clean_shutdown_oplog_state] "advice" : "A corrupt namespace has been detected. See http://dochub.mongodb.org/core/data-recovery for recovery steps.",
[js_test:clean_shutdown_oplog_state] "ok" : 1
[js_test:clean_shutdown_oplog_state] }
"thread":"60938:0xffff91eaee00","session_dhandle_name":"file:index-70-8170640145721574010.wt","session_name":"WT_SESSION.verify","category":"WT_VERB_DEFAULT","category_id":9,"verbose_level":"ERROR","verbose_level_id":-3,"msg":"__verify_row_key_order_check:263:the 111 and 113 keys on page at [0: 5681152-5689344, 8192, 1599360406] are incorrectly sorted: -\\07\\0e,\\04, -\\07\\0a\\e4\\04" "thread":"60938:0xffff91eaee00","session_dhandle_name":"file:index-70-8170640145721574010.wt","session_name":"WT_SESSION.verify","category":"WT_VERB_DEFAULT","category_id":9,"verbose_level":"ERROR","verbose_level_id":-3,"msg":"__verify_ckptfrag_chk:520:checkpoint ranges never verified: 98" "thread":"60938:0xffff91eaee00","session_dhandle_name":"file:index-70-8170640145721574010.wt","session_name":"WT_SESSION.verify","category":"WT_VERB_DEFAULT","category_id":9,"verbose_level":"ERROR","verbose_level_id":-3,"msg":"__verify_filefrag_chk:434:file ranges never verified: 98"
This ticket has been created after initial triage. I ran the failing test clean_shutdown_oplog_state.js over 70k times, spread out between recent wiredtiger changes that we thought could have caused this issue (WT-8170, WT-8745, WT-8626, WT-8362, WT-8652). The bug never reproduced. keith.bostic also doesn't think that these tickets are responsible. Further investigation is needed to root cause of this issue.
More details in the related build failure ticket.