Operational Defect Database
BugZero found this defect 53 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2624101
$_testApiVersion prevents recoverFromOplogAsStandalone
Last update date:
3/27/2024
Affected products:
MongoDB Server
Affected releases:
6.0.14
Fixed releases:
No fixed releases provided.
Description:
Info
mongod crashes when I try to revive its artifacts from a mongosync test run with recoverFromOplogAsStandalone. Found while investigating REP-4286, in which the change stream seems to have “omitted” a dropDatabase. Maybe these issues are related? Thank you!
Top User Comments
Steps to Reproduce
evergreen fetch --artifacts --task mongosync_v60_to_v60_rhel80_ctc_single_shard_terminate_primary_jscore_passthrough_v60_to_v60_a59aa8c4f83d988bfba9416d667e877ac9fb18b7_24_03_21_21_38_13 cd artifacts-a59aa8-v60-to-v60-rhel80_ctc_single_shard_terminate_primary_jscore_passthrough_v60_to_v60 tar -xvzf mongo-data-mongosync_v60_to_v60_rhel80_ctc_single_shard_terminate_primary_jscore_passthrough_.tgz cd data/db/job9/cluster0/job9/resmoke/shard0/node0 mongod-6.0 -setParameter recoverFromOplogAsStandalone=true --dbpath . OBSERVE: mongod crashes. EXPECTED: mongod should recover from the oplog and function normally. NB: Without recoverFromOplogAsStandalone, mongod does not crash.
