-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
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.
- is related to
-
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-