[SERVER-28898] sync fails when large update follow by replica set config Created: 21/Apr/17  Updated: 29/Jan/18  Resolved: 08/May/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.4.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Calin Pirtea Assignee: Mark Agarunov
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

have 10 nodes in a replication set iwth only 1 primary.
have node 11 on standby (ready to add to set)
allowChaining must be true

perform large update on primary followed immediately by updating replication set config to add node 11.

some secondaries that sync to other secondaries will fail with "Restarting oplog query due to error: ExceededTimeLimit: Operation timed out, request was RemoteCommand..."

the longer the chain of secondary->secondary->secondary...->primary the more likely sync will hang.

Participants:

 Description   

sync fails when large update follow by replica set config



 Comments   
Comment by Mark Agarunov [ 08/May/17 ]

Hello pcalin,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Thanks,
Mark

Comment by Ramon Fernandez Marina [ 24/Apr/17 ]

Can you please provide the log files? Would be useful to see the primary node, and all the nodes in the replication chain between those two.

Thanks,
Ramón.

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