Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
ALL
Description
During a replica set reconfig, each node independently increments and installs the new config. While this is happening, it is possible for a node to attempt to run an updatePosition command on a sync source node with a different config version than its own. Currently, the code tries again immediately until the config versions between the two nodes becomes the same and the updatePosition command finally succeeds; this can result in heavy network traffic.
One stopgap solution to this problem is to put in a sleep between retries.
Attachments
Issue Links
- is related to
-
SERVER-16272 SyncSourceFeedback spams log on errors
-
- Closed
-
- related to
-
SERVER-26494 remove unreachable else-branch in sync_source_feedback.cpp logic
-
- Closed
-
-
SERVER-27397 Disable OplogFetcher sync source re-evaluation during initial sync
-
- Closed
-