[SERVER-77911] Shard merge importing collection without timestamp can trigger invariant failure in HistoricalCatalogIdTracker. Created: 08/Jun/23 Updated: 29/Oct/23 Resolved: 14/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Suganthi Mani |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Serverless
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Server Serverless 2023-07-10, Server Serverless 2023-07-24, Server Serverless 2023-08-07, Server Serverless 2023-08-21 | ||||
| Participants: | |||||
| Linked BF Score: | 105 | ||||
| Description |
|
Shard merge does non-timestamped catalog writes when importing collections (i,e, collections created during physical cloning phase). But, does timestamped catalog writes when dropping those collections. This mixed timestamp mode usage can trigger invariant failure in HistoricalCatalogIdTracker which was introduced to support point-in-time catalog lookups PM-2218.
Noting the problematic sequence here.
|
| Comments |
| Comment by Githook User [ 14/Aug/23 ] |
|
Author: {'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}Message: |
| Comment by Suganthi Mani [ 14/Aug/23 ] |
|
Just for the ticket watchers, filed |