[SERVER-78545] CheckMetadataConsistency hook should retry on FailedToSatisfyReadPreference Created: 29/Jun/23 Updated: 29/Oct/23 Resolved: 03/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pol Pinol | Assignee: | Pol Pinol |
| 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: |
v7.0
|
||||||||
| Sprint: | Sharding EMEA 2023-07-10 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 150 | ||||||||
| Description |
|
When there is a stepdown, and there is no stepup for more than 15 seconds, CheckMetadataConsistency hook will throw a FailedToSatisfyReadPreference. This can happen with slow machines, when the node is slow in shutting down, and the cluster remains without a primary for a long time. As the CheckMetadataConsistency hook is continuously being run, I propose to abort the hook if a FailedToSatisfyReadPreference error is found. |
| Comments |
| Comment by Githook User [ 05/Jul/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: (cherry picked from commit ea8f29ffa43c6245551993d3761c271332a87e66) |
| Comment by Githook User [ 03/Jul/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: |