[SERVER-33026] SyncSourceFeedback request doesn't have a timeout Created: 30/Jan/18 Updated: 29/Oct/23 Resolved: 15/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.15, 3.6.5, 3.7.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | William Schultz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v3.6, v3.4
|
||||||||||||
| Sprint: | Repl 2018-03-12, Repl 2018-03-26 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
If the remote drops the request, SyncSourceFeedback will not recover in time even if the secondary has already been syncing from another healthy sync source. |
| Comments |
| Comment by Githook User [ 23/Apr/18 ] |
|
Author: {'email': 'william.schultz@mongodb.com', 'username': 'will62794', 'name': 'William Schultz'}Message: This patch ensures that replSetUpdatePosition commands that are sent from a replica (cherry picked from commit d0dea93d632ce451b66b57b538e66f3e1378b049) |
| Comment by Githook User [ 23/Apr/18 ] |
|
Author: {'email': 'william.schultz@mongodb.com', 'username': 'will62794', 'name': 'William Schultz'}Message: This patch ensures that replSetUpdatePosition commands that are sent from a replica (cherry picked from commit d0dea93d632ce451b66b57b538e66f3e1378b049) |
| Comment by Githook User [ 15/Mar/18 ] |
|
Author: {'email': 'william.schultz@mongodb.com', 'name': 'William Schultz', 'username': 'will62794'}Message: This patch ensures that replSetUpdatePosition commands that are sent from a replica |
| Comment by Bruce Lucas (Inactive) [ 02/Feb/18 ] |
|
The observed impact of this is that when a network partition or host down occurs, after sync source is re-established lag never goes below 2 seconds, so all operations that depend on majority commit (e.g. read or write concern majority) experience a minimum latency of 2 seconds. |