[SERVER-67956] Update to blocking state is not written at the blockTimestamp Created: 11/Jul/22 Updated: 29/Oct/23 Resolved: 12/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Matt Broadstone |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-07-25 |
| Participants: |
| Description |
|
A recent refactor of the updateStateDocument method had an unintended side effect of no longer writing updates to the reserved oplog slot. |
| Comments |
| Comment by Githook User [ 12/Jul/22 ] |
|
Author: {'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}Message: |