[SERVER-84060] Insert Notifier code needs to be robust to clock changes Created: 11/Dec/23 Updated: 14/Dec/23 Resolved: 14/Dec/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| 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 2023-12-25 | ||||
| Participants: | |||||
| Linked BF Score: | 135 | ||||
| Description |
|
The waitForInsertNotifier code (used for awaitData queries, typically on the oplog) in both the classic and SBE plan executors currently expects that if "shouldWaitForInserts" returns false, it will never return true for that particular query. It turns out that this assumption is not true if the system clock can go backwards; we need to protect against that case. |
| Comments |
| Comment by Githook User [ 13/Dec/23 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: GitOrigin-RevId: 06a4067f0eea4ca0fb96581aa1e2c01c07c72c30 |