Apply replicated inserts as inserts

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 3.1.6
    • Affects Version/s: None
    • Component/s: Replication
    • Fully Compatible
    • RPL 6 07/17/15
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • 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).

            Assignee:
            Scott Hernandez (Inactive)
            Reporter:
            Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            17 Start watching this issue

              Created:
              Updated:
              Resolved: