[SERVER-72618] Untimestamped writes to the catalog can occur when dropping unfinished indexes during replication rollback Created: 09/Jan/23 Updated: 29/Oct/23 Resolved: 18/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| 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 | ||||||||||||||||||||
| Sprint: | Execution Team 2023-01-23 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 58 | ||||||||||||||||||||
| Description |
|
During replication rollback, all index builds are stopped. When reopening the catalog, any unfinished index builds that weren't secondary background index builds have their index entry in the catalog dropped. This performs an untimestamped write. There's no oplog entry associated with this write, but we can probably use the common point timestamp the node rolled back to. |
| Comments |
| Comment by Githook User [ 18/Jan/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |