[SERVER-31084] ReplSetTest dumpOplog function should print entire oplog at once with jsTestLog Created: 13/Sep/17 Updated: 30/Oct/23 Resolved: 16/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Judah Schvimer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
The dumpOplog function in ReplSetTest prints out the oplog of a given node by iterating over each element in a cursor on that node's oplog. Since it makes a separate print call for each oplog entry, the output can get interleaved with other log messages, making it harder to read the oplog entries in order. We should improve this by building up a JSON string of all the oplog entries first, and then printing it with one call to jsTestLog. |
| Comments |
| Comment by Githook User [ 16/Oct/17 ] |
|
Author: {'email': 'judah@mongodb.com', 'name': 'Judah Schvimer', 'username': 'judahschvimer'}Message: |