[SERVER-50914] cursor_valid_after_shard_stepdown.js can fail because of an unintended metadata refresh Created: 14/Sep/20 Updated: 29/Oct/23 Resolved: 22/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0, 4.4.2, 4.2.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Jordi Serra Torrens |
| 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 | ||||||||||||||||
| Steps To Reproduce: | 1. The primary node steps down as part of the test |
||||||||||||||||
| Sprint: | Sharding 2020-11-02 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 25 | ||||||||||||||||
| Description |
|
When running the sharding_csrs_continuous_config_stepdown suite, the cursor_valid_after_shard_stepdown.js test expects to have stale sharding metadata, but the following scenario might happen: 1. The primary node steps down as part of the test One way to solve this is to disable the periodic index check like this test |
| Comments |
| Comment by Jordi Serra Torrens [ 22/Oct/20 ] |
|
It was already fixed on |