[SERVER-47907] Remove unnecessary shard from index_commands_shard_targeting.js Created: 01/May/20 Updated: 29/Oct/23 Resolved: 28/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Cheahuychou Mao |
| 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 | ||||||||||||||||
| Sprint: | Sharding 2020-06-01 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 28 | ||||||||||||||||
| Description |
|
jstests/sharding/index_commands_shard_targeting.js verifies the commands that modify indexes check shard versions and trigger metadata refreshes. After an index command triggers a refresh, it asserts that a shard was not targeted did not refresh its metadata, which may or may not be true depending on the binary of the mongos that ran the command, because of the removal of the ShardConnection::checkMyConnectionVersions() call between stale config retries by Instead of blacklisting this test from the mixed version suites, the assertions on the extra shard can be removed since they don't affect the test's intended coverage. |
| Comments |
| Comment by Githook User [ 28/May/20 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}Message: |
| Comment by Jack Mulrow [ 01/May/20 ] |
|
Removing the extra shard makes this test fail because of the issue described in |