[SERVER-47012] Make it more obvious that retryIdempotentWorkUntilSuccess will stop retrying if the node has stepped down Created: 20/Mar/20 Updated: 29/Oct/23 Resolved: 27/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.3.4 |
| Fix Version/s: | 4.4.0-rc0, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| 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: |
v4.4
|
||||||||||||
| Sprint: | Sharding 2020-03-23, Sharding 2020-04-06 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Otherwise, if the node stepped down and term was updated just before the term was saved, the operation will keep getting retried even while the node is secondary, until the node becomes primary again (which may never happen). This is particularly painful because a warning message will keep being logged. |
| Comments |
| Comment by Githook User [ 30/Mar/20 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: (cherry picked from commit c60e8ce46af84d273648bc49c495e44f08ea1fb0) |
| Comment by Githook User [ 27/Mar/20 ] |
|
Author: {'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}Message: |