[SERVER-64457] secondary_reads_waitForShardingInit.js does not force mongos choose the right shard Created: 11/Mar/22 Updated: 29/Oct/23 Resolved: 14/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sophia Tan | Assignee: | Sophia Tan |
| 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 | ||||
| Participants: | |||||
| Linked BF Score: | 35 | ||||
| Description |
|
in secondary_reads_waitForShardingInit.js, we expect the mongos always send the request to the hanging secondary node. But, the test code does not force mongos to choose the shard which has that node. If mongos send request to another shard, the test will fail. BF-24464 hit this error case. To fix it, we should force the mongos choose the right shard. Also, in this js file, the way of using session should be improved too. |
| Comments |
| Comment by Githook User [ 14/Mar/22 ] |
|
Author: {'name': 'Sophia Tan', 'email': 'sophia_tll@hotmail.com', 'username': 'sophiatll'}Message: |