[SERVER-56720] Ensure original primary steps back up in timeseries_retryable_write_downgrade.js Created: 06/May/21 Updated: 29/Oct/23 Resolved: 18/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | post-rc0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2021-05-31 | ||||
| Participants: | |||||
| Linked BF Score: | 20 | ||||
| Description |
|
In timeseries_retryable_write_downgrade.js, after downgrading the replica set, the original primary is required to become primary again so that we can perform an insert using the existing session. However, the current code that attempts to do this does not properly provide this guarantee. timeseries_retryable_write_downgrade_oplog_rollover, which is based off of this test, has updated logic for this which should work correctly. |
| Comments |
| Comment by Githook User [ 18/May/21 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |