[SERVER-72077] Make write distribution metrics calculation account for the replacement update case Created: 13/Dec/22 Updated: 29/Oct/23 Resolved: 16/Dec/22 |
|
| 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: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding NYC 2022-12-26 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
For an update that doesn't filter by shard key equality, if it is not an upsert, we allow the it to be targeted by the shard key extracted from the replacement document. The metrics calculation should account for that case. |
| Comments |
| Comment by Githook User [ 16/Dec/22 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |