[SERVER-71033] Deserialize NamespaceString correctly during rollback Created: 02/Nov/22 Updated: 29/Oct/23 Resolved: 12/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Hugh Tong (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Serverless
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2023-01-09, Server Serverless 2023-01-23 |
| Participants: |
| Description |
|
As a part of the process to rollback to a stable timestamp, we walk through the local oplog to find all of the ops that will be rolled back and store information from each of these oplog entries, including the namespace the op belongs to. For any NamespaceString objects that we manually construct when walking this file, we should call NamespaceStringUtil::deserialize and pass the tenantId from the oplogEntry to it. Those places are:
|
| Comments |
| Comment by Githook User [ 13/Jan/23 ] |
|
Author: {'name': 'Hugh Tong', 'email': 'hugh.tong@mongodb.com', 'username': 'cortrain'}Message: |