[SERVER-36867] Change votes for config rs to 0 so that secondaries cannot step up in event of config stepdown in primary_config_server_blackholed_from_mongos.js Created: 24/Aug/18 Updated: 29/Oct/23 Resolved: 05/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2018-11-19 | ||||
| Participants: | |||||
| Linked BF Score: | 1 | ||||
| Description |
|
If the primary config steps down in primary_config_server_blackholed_from_mongos.js and a different node steps up, the bridge will not be able to blackhole mongos from the config and reading with readPref primary will pass, thus failing the test. We should change the votes and priority for the config secondaries to 0 so that they cannot step up. |
| Comments |
| Comment by Githook User [ 05/Nov/18 ] |
|
Author: {'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: |