[SERVER-59653] Account for RSM host timeout in random_moveChunk_index_operations.js and refine_collection_shard_key_nested_zone_ops.js Created: 27/Aug/21 Updated: 05/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jason Zhang | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Cluster Scalability
|
||||
| Operating System: | ALL | ||||
| Sprint: | Sharding NYC 2023-10-16, Sharding NYC 2023-10-30, Cluster Scalability 2023-11-13, Cluster Scalability 2023-11-27, Cluster Scalability 2023-12-11, Cluster Scalability 2023-12-25, Cluster Scalability 2024-1-8, Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5, Cluster Scalability 2024-2-19 | ||||
| Participants: | |||||
| Linked BF Score: | 11 | ||||
| Description |
|
We should account for the fact that the RSM could timeout while discovering the new primary by allowing FailedToSatisfyReadPreference errors in the test. |
| Comments |
| Comment by Wenqin Ye [ 30/Oct/23 ] |
|
Closing my PR because I realized this does not actually fix the BF I was investigating (BF-30474). BF-30474 ended up being due to some server code issue that this test change does not address. I'm not going to close this SERVER ticket entirely because it may still be needed to fix BF-22214. |