[SERVER-37657] Report the offending oplog entries if a batch contains non-increasing transaction numbers Created: 18/Oct/18 Updated: 29/Oct/23 Resolved: 22/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.9, 4.0.4, 4.1.5 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.0, v3.6
|
||||||||
| Sprint: | Sharding 2018-10-22, Sharding 2018-11-05 | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
If this invariant trips, currently it is impossible to figure out exactly what was the state of the oplog batch on the secondary node without getting the entire oplog and scanning through it. This is problematic from supportability point of view since it requires customers to upload their entire oplog, which could be quite large. Instead, we should include as much information as possible in the mongodb log before crashing the server to help us diagnose this invariant. |
| Comments |
| Comment by Githook User [ 23/Oct/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: (cherry picked from commit 826c8b47c283749bb6f751d57729c6c3ac160a75) |
| Comment by Githook User [ 22/Oct/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: (cherry picked from commit 16e139c29350840b1b026164c71e998b71ada2be) |
| Comment by Githook User [ 22/Oct/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |