[SERVER-22679] fix confusing 'no such command _id' message from rollback_fake_cmd.js output Created: 17/Feb/16  Updated: 25/Jan/17  Resolved: 17/Feb/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.3.2

Type: Improvement Priority: Trivial - P5
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Participants:
Linked BF Score: 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



 Comments   
Comment by Githook User [ 17/Feb/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-22679 fixed rollback_fake_cmd.js oplog entry to ensure fake command name is reported in logs.
Branch: master
https://github.com/mongodb/mongo/commit/1a74a81b6eb2ad4b3fdd30408b522826aa08610c

Generated at Thu Feb 08 04:01:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.