[SERVER-59056] [5.0] Fix primary check in timeseries_retryable_write_downgrade.js Created: 03/Aug/21 Updated: 29/Oct/23 Resolved: 06/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| 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 | ||||
| Sprint: | Execution Team 2021-08-09 | ||||
| Participants: | |||||
| Linked BF Score: | 49 | ||||
| Description |
|
In timeseries_retryable_write_downgrade.js, we check whether the primary is not the same as the original primary in order to determine whether we need to step up the secondary. However, it turns out that after the node has been restarted, this check always evaluates to false. One way to fix this is to check equality of the ports instead. |
| Comments |
| Comment by Githook User [ 05/Aug/21 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |