[SERVER-61476] Handle missing sizeStorer info in Merge Created: 15/Nov/21 Updated: 19/Aug/23 Resolved: 03/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | A. Jesse Jiryu Davis | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | shard-merge-milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Serverless
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
A recently-created donor collection may have no info in the "sizeStorer" WT table, so the recipient has no numRecords or dataSize for the collection. Determine when this happens and how to handle it in Merge. Also, ensure that wrong donor sizeStorer info is eventually corrected on the recipient. Milestone 3. |
| Comments |
| Comment by Suganthi Mani [ 03/Mar/23 ] |
|
We agreed that shard merge don’t ensure fast count (See the design doc) |
| Comment by Mathis Bessa [ 19/Aug/22 ] |
|
We should also re-introduce the validate_collection check in the tenant migration passthrough. We have an issue where we can have mismatch between fast count and on-disk record count for imported donor collections and as a result we temporary disabled that check until this ticket change is done. SERVER-61147 is the ticket introducing the vanilla passthrough and disabling the check for shard merge. |