[SERVER-58871] Set fixed db primary in write_concern_basic.js Created: 27/Jul/21 Updated: 29/Oct/23 Resolved: 28/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.4, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| 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 | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Sprint: | Sharding EMEA 2021-08-09 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 154 | ||||||||
| Description |
|
write_concern_basic.js needs to set a fixed db primary to make sure that this failpoint is always set on the non db-primary shard, regardless of what the db primary happens to be in a particular test run. |
| Comments |
| Comment by Githook User [ 21/Oct/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: (cherry picked from commit 9b87aa49a79d4018f8de9ec2c95fd2742f3b8303) |
| 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 [ 28/Jul/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |
| Comment by Jordi Serra Torrens [ 27/Jul/21 ] |
|
You are right. Setting a fixed db-primary is cleaner. I'll repurpose the ticket. |
| Comment by Kaloian Manassiev [ 27/Jul/21 ] |
|
Another option is to pass a fixed primary for every run of the test so that it doesn't get randomised. |