[SERVER-66074] Remove usage of toArray in collection_defragmentation.js Created: 29/Apr/22 Updated: 29/Oct/23 Resolved: 31/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc10, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v6.0
|
||||||||
| Steps To Reproduce: | Setting numChunks to >130 and running in concurrency_sharded_with_stepdowns_and_balancer ensures this failure happens pretty regularly |
||||||||
| Sprint: | Sharding EMEA 2022-06-13 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 29 | ||||||||
| Description |
|
The mergeChunks state of collection_defragmentation.js gets all chunks from config.collections using toArray. If there are a lot of chunks (usually >100 needed) this can require a call to getMore which will fail if the test is being run on a suite that involves stepdowns (concurrency_sharded_with_stepdowns_and_balancer, concurrency_sharded_kill_primary_with_balancer, etc.). In order to allow the test to continue running on these suites, we should remove the call to toArray and simply check a random subset of the chunks for mergeability in each mergeChunks phase so that getMore is not called. |
| Comments |
| Comment by Githook User [ 10/Jun/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit 2a61fb48311b141c92bb0185fe7cb3caa0480ac0) |
| Comment by Githook User [ 31/May/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |