[SERVER-38640] Do not update committed snapshot with null OpTime Created: 14/Dec/18 Updated: 29/Oct/23 Resolved: 19/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Tess Avitabile (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 | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2019-01-14 | ||||
| Participants: | |||||
| Linked BF Score: | 45 | ||||
| Description |
|
When enableMajorityReadConcern='false', the stable optime can be ahead of the last committed optime, so the replication coordinator updates the committed snapshot based on the last committed optime instead of the stable optime. This causes a crash if the last committed optime is null, since _updateCommittedSnapshot_inlock() expects a non-null optime. We should not call _updateCommittedSnapshot_inlock() when the last committed optime is null. |
| Comments |
| Comment by Githook User [ 19/Dec/18 ] |
|
Author: {'username': 'tessavitabile', 'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile'}Message: |