-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.6.11, 3.0.5
-
Component/s: Replication
-
None
-
Replication
-
ALL
-
-
(copied to CRM)
Assuming a constant stream of operations totalling 50MB/s data (eg. insertions) to a replica-set, any Secondary that has more than ~40ms network latency (~80ms ping) to its next nearest member will be unable to keep up regardless of the network bandwidth between them.
If the ping time between any two members of a replica set is known, the upper limit for replication throughput in MB/s between those two members can be calculated with the following equation:
4 * 1000 / ping_time_in_ms
The limit arises because the tailable cursor retrieves at max 4MB per roundtrip but the request/reply is serial. Thus, the longer a roundtrip (ping) takes, the lower the throughput.
- depends on
-
SERVER-28511 OP_MSG Exhaust support for mongod ingress layer and DBClient
- Closed
- is related to
-
SERVER-21797 Simplify find batching logic
- Closed