[SERVER-36469] shard_kill_and_pooling isn't querying the shard it's supposed to Created: 06/Aug/18 Updated: 29/Oct/23 Resolved: 18/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.14, 4.0.11, 4.2.0-rc2, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Blake Oler |
| 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: |
v4.2, v4.0, v3.6
|
||||
| Sprint: | Sharding 2019-07-01 | ||||
| Participants: | |||||
| Description |
|
The test is broken but has been silently passing since most of the time the second shard gets selected as the shard primary, and thus no queries get sent to the first shard, which is the shard that is getting restarted by the test. We should either remove the second shard or use ensurePrimaryShard to force the test to query against the shard that is being restarted by the test. |
| Comments |
| Comment by Githook User [ 25/Jun/19 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: (cherry picked from commit c84cc4eee31704f5c0257512b48b7e2513515ef7) |
| Comment by Githook User [ 25/Jun/19 ] |
|
Author: {'name': 'Blake Oler', 'username': 'BlakeIsBlake', 'email': 'blake.oler@mongodb.com'}Message: (cherry picked from commit c84cc4eee31704f5c0257512b48b7e2513515ef7) |
| Comment by Githook User [ 24/Jun/19 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: (cherry picked from commit c84cc4eee31704f5c0257512b48b7e2513515ef7) |
| Comment by Githook User [ 18/Jun/19 ] |
|
Author: {'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}Message: |