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

fix confusing 'no such command _id' message from rollback_fake_cmd.js output

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Trivial - P5 Trivial - P5
    • 3.3.2
    • None
    • Replication
    • None
    • Fully Compatible
    • 0

    Description

      rollback_fake_cmd.js tests the server's ability to rollback an oplog entry containing a nonexistent command name - in the current test script, it reuses an oplog entry from a collection insertion as the command object which leads to the following confusing test output:

      2016-02-06T06:51:43.333+0000 I -        [rsBackgroundSync] Fatal assertion 28723 UnrecoverableRollbackError: rollback no such command _id @ 18751
      

      Attachments

        Activity

          People

            benety.goh@mongodb.com Benety Goh
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: