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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Trivial - P5
    • 3.3.2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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
      

              Assignee:
              Benety Goh
              Reporter:
              Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: