[SERVER-53967] scaled_collection_stats.js should use _waitForDelete in moveChunk Created: 22/Jan/21 Updated: 29/Oct/23 Resolved: 04/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Sharding-EMEA, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding 2021-02-08 | ||||
| Participants: | |||||
| Linked BF Score: | 23 | ||||
| Description |
|
In this moveChunk we should pass {_waitForDelete: true} to ensure that when the moveChunk command returns, the range deletion (which is started by the move chunks but executes asynchronously) has finished. If we don't do this, this $collStats could return a totalIndexSize different than what it will be after the range deletion has actually finished. |
| Comments |
| Comment by Githook User [ 04/Feb/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |