[SERVER-62233] Make SessionCatalogMigrationSource handleWriteHistory filter out oplogs outside of the chunkRange with OpType 'n' Created: 22/Dec/21 Updated: 29/Oct/23 Resolved: 14/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Luis Osta (Inactive) | Assignee: | Luis Osta (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2022-01-10, Sharding 2022-01-24 | ||||||||
| Participants: | |||||||||
| Story Points: | 4 | ||||||||
| Description |
|
Background The call to getNextSessionOplogBatch by the destination shard should only return oplogs that adhere to the following conditions:
The Problem The SessionCatalogMigrationSource won't filter out the oplog entries that are outside of the migrating chunk range if the oplog has been rewritten to have a OpType of 'n'. Which is what happens as part of session migration. This causes the performance issue discovered in Classes Involved:
Solution
|
| Comments |
| Comment by Githook User [ 14/Jan/22 ] |
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: |