-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
RPL 6 07/17/15
Replicated inserts are currently processed on secondaries as an update (w/upsert:true), not an insert as an extra, but unnecessary, guarantee for idempotency. This is more expensive than the original insert on the primary so it cause differences in performance on secondary, like increased resource allocation (cpu) and/or latency (replication lag).
- is depended on by
-
SERVER-18908 Secondaries unable to keep up with primary under WiredTiger
- Closed
- related to
-
SERVER-30049 applyOperation_inlock() allows exceptions from Collection::insertDocument() to percolate to caller
- Closed
-
SERVER-30106 Allow syncTail replication to write to drop-pending collections
- Closed