[SERVER-31062] Add more detailed diagnostics for rollback via refetch (rs_rollback.cpp) Created: 12/Sep/17 Updated: 30/Oct/23 Resolved: 14/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | William Schultz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Repl 2017-10-02, Repl 2017-10-23, Repl 2017-11-13, Repl 2017-12-04 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
To facilitate general debugging and coverage metrics for randomized rollback testing, we should add additional logging into the rollback process that describes what is being done more comprehensively. This may include the following:
These messages could be placed at a higher log level that we can enable in our tests. |
| Comments |
| Comment by Githook User [ 18/Oct/17 ] |
|
Author: {'email': 'judah@mongodb.com', 'name': 'Judah Schvimer', 'username': 'judahschvimer'}Message: |
| Comment by Githook User [ 16/Oct/17 ] |
|
Author: {'email': 'william.schultz@mongodb.com', 'name': 'William Schultz', 'username': 'will62794'}Message: |
| Comment by Githook User [ 10/Oct/17 ] |
|
Author: {'email': 'william.schultz@mongodb.com', 'name': 'William Schultz', 'username': 'will62794'}Message: |
| Comment by Judah Schvimer [ 26/Sep/17 ] |
|
At every step in rollback we log what we did (example), but only after the fact. If there's an error while doing an operation like an fassert creating an index, it's not easy to tell what we were trying to do that failed. We should add a log before every operation so it's easier to see what went wrong when something does go wrong. |