Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-88630

$_testApiVersion prevents recoverFromOplogAsStandalone

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 6.0.14
    • Component/s: None
    • Labels:
      None
    • Replication
    • ALL
    • Hide
      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.

      Show
      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.
    • Repl 2024-04-15, Repl 2024-04-29, Repl 2024-05-13

      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!

            Assignee:
            ali.mir@mongodb.com Ali Mir
            Reporter:
            felipe.gasper@mongodb.com Felipe Gasper
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: