[SERVER-81878] startupRecoveryForRestore may not play nicely with collection drop applied during startup recovery Created: 04/Oct/23 Updated: 27/Dec/23 Resolved: 15/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.0, 4.4.7 |
| Fix Version/s: | 4.4.27, 5.0.24 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Requested: |
v5.0, v4.4
|
||||||||||||||||||||||||
| Sprint: | Execution Team 2023-11-13, Execution Team 2023-11-27 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||
| Description |
|
On v5.0, when using recoverFromOplogAsStandalone, after recovering from the oplog we set the internal readOnly flag to true. If also using startupRecoveryForRestore, we have also advanced the oldest timestamp during the oplog application, as described in |
| Comments |
| Comment by Githook User [ 29/Nov/23 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 3e7169f6c0433cac7f6b60271335cae30179e6b8) GitOrigin-RevId: 27546df3ba66a7a12488c71cfa0b71a43f83490e |
| Comment by Githook User [ 15/Nov/23 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |
| Comment by Gregory Noma [ 15/Nov/23 ] |
|
Upon further inspection I think this is actually also fixed on 6.0 because of |
| Comment by Gregory Noma [ 14/Nov/23 ] |
|
I believe this is fixed as of 6.1 thanks to |
| Comment by Steven Vannelli [ 05/Oct/23 ] |
|
We need to understand which branches this affects and think through potential solutions. |