[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: |
|
||||
| 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:
|
| 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: |