[SERVER-59684] Blacklist cursor_valid_after_shard_stepdown from sharding_max_mirroring Created: 31/Aug/21 Updated: 29/Oct/23 Resolved: 03/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| 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: | 28 | ||||
| Description |
|
cursor_valid_after_shard_stepdown assumes that the secondary has no information about the collection on step up. In the max mirroring suite, though, the secondary can have an up to date view of the collection because of mirroring reads, and so the assertion that shardversion should be unknown after step up will not always be true. We should prevent this test from running in the max mirroring suite, and provide a comment in the test about the problem, in case this causes issues for other tests and the assertion of unknown version needs to be removed. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 03/Sep/21 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |