[SERVER-52659] Avoid running command in a separate thread in index_commands_shard_targeting.js Created: 06/Nov/20 Updated: 29/Oct/23 Resolved: 08/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2020-11-16 |
| Participants: |
| Description |
|
index_commands_shard_targeting.js is running index related command in a separate thread and in parallel waiting for a log line to eventually appear on shard0. There is no need to run these steps in parallel, in fact we can run the command, assert that it will fail and then search in the log lines of shard0, all in an old-fashion sequential approach |
| Comments |
| Comment by Githook User [ 06/Nov/20 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |