[SERVER-63607] Ensure cursor_valid_after_shard_stepdown.js test leaves eligible primaries Created: 14/Feb/22 Updated: 29/Oct/23 Resolved: 14/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.3.0 |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| 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: | 25 | ||||
| Description |
|
cursor_valid_after_shard_stepdown.js steps down a node and prevent elections for 60 seconds, afterwards when the ShardingTest try to shutdown the cluster and perform the cleanup check it can't find a primary for that shard. The solution would be to unfreeze the stepped down node so that a new primary would be elected before the ShardingTest shutdown. |
| Comments |
| Comment by Githook User [ 14/Feb/22 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |