Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.1.6
Affects Version/s: None
Component/s: Replication
Labels:
- mms-s

Backwards Compatibility:
Fully Compatible
Sprint:
RPL 6 07/17/15
Confidence Status:
None
Work Order:
0

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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

Assignee:: Scott Hernandez (Inactive)

Reporter:: Bruce Lucas (Inactive)

Participants:: Bruce Lucas, Githook User, Scott Hernandez

Votes:: 0 Vote for this issue

Watchers:: 17 Start watching this issue

Created:: Jun 15 2015 07:49:03 PM UTC

Updated:: Jul 24 2017 03:31:49 PM UTC

Resolved:: Jul 20 2015 09:11:11 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates