[SERVER-62672] Avoid `getCollectionVersion` duplicate queries when committing chunk operations Created: 14/Jan/22 Updated: 29/Oct/23 Resolved: 20/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26 |
| Participants: | |
| Story Points: | 3 |
| Description |
|
The getCollectionVersion method performs a query on config.collections before getting the version. When committing chunk operations, the call is preceded or followed by the exact same query (e.g. when committing a merge). Objective of this ticket is to optimize the flow by allowing passing a CollectionEntry to the method in order to avoid executing the same query two times. |
| Comments |
| Comment by Githook User [ 20/Dec/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |