[SERVER-48278] Fix waits for RSM removal in sharding/remove2.js test Created: 18/May/20 Updated: 29/Oct/23 Resolved: 18/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2020-06-01 | ||||
| Participants: | |||||
| Linked BF Score: | 24 | ||||
| Description |
|
sharding/remove2.js is waiting for the ReplicaSetMonitor timeout in order to be able re-add a shard after its removal. Instead of waiting 60s for the RSM to be removed from the interesting nodes, pols the connectionsPoolStats of these nodes until it is actually removed. The new polling approach is reducing the test execution time on Enterprise RHEL 6.2 run time form ~2:40 to ~1:40 This commit also unblacklist the sharding/remove2.js test from the multiversion suites. Because the new polling approach solves BF-17247. |
| Comments |
| Comment by Githook User [ 18/May/20 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: `sharding/remove2.js` is waiting for the ReplicaSetMonitor timeout in order to be able re-add a shard after its removal. Instead of waiting 60s for the RSM to be removed from the interesting nodes, pols the connectionsPoolStats of these nodes until it is actually removed. The new polling approach is reducing the test execution time on Enterprise RHEL 6.2 run time form ~2:40 to ~1:40 This commit also unblacklist the sharding/remove2.js test from the multiversion suites. Because the new polling approach solves BF-17247. |