[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:
Backports
Related
is related to SERVER-32703 Secondary can take a couple minutes t... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6, v3.4
Sprint: Repl 2018-03-12, Repl 2018-03-26
Participants:
Case:

 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: SERVER-33026 SyncSourceFeedback request should have a timeout

This patch ensures that replSetUpdatePosition commands that are sent from a replica
set node to its sync source have a network timeout. Previously these network
requests were not given any timeouts.

(cherry picked from commit d0dea93d632ce451b66b57b538e66f3e1378b049)
Branch: v3.4
https://github.com/mongodb/mongo/commit/fa2f9cd2dacf7aa035b08eab200d45681b16d938

Comment by Githook User [ 23/Apr/18 ]

Author:

{'email': 'william.schultz@mongodb.com', 'username': 'will62794', 'name': 'William Schultz'}

Message: SERVER-33026 SyncSourceFeedback request should have a timeout

This patch ensures that replSetUpdatePosition commands that are sent from a replica
set node to its sync source have a network timeout. Previously these network
requests were not given any timeouts.

(cherry picked from commit d0dea93d632ce451b66b57b538e66f3e1378b049)
Branch: v3.6
https://github.com/mongodb/mongo/commit/0b032b7f56520fcbd58a581cf9ff943c5d5c62ed

Comment by Githook User [ 15/Mar/18 ]

Author:

{'email': 'william.schultz@mongodb.com', 'name': 'William Schultz', 'username': 'will62794'}

Message: SERVER-33026 SyncSourceFeedback request should have a timeout

This patch ensures that replSetUpdatePosition commands that are sent from a replica
set node to its sync source have a network timeout. Previously these network
requests were not given any timeouts.
Branch: master
https://github.com/mongodb/mongo/commit/d0dea93d632ce451b66b57b538e66f3e1378b049

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.

Generated at Thu Feb 08 04:32:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.