Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-22530

improve capped collection replicated inserts

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.2
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.2
    • Steps To Reproduce:
      Hide

      Run the insert_capped.js workload on a replica set to see the issue.

      Show
      Run the insert_capped.js workload on a replica set to see the issue.
    • Sprint:
      Repl 10 (02/19/16)

      Description

      Vectored insert does not support inserting into a capped collection, so if you do more than a light load of inserts into a capped collection, secondaries will flood their logs with:

      2016-02-08T17:00:21.539-0500 E REPL     [repl writer worker 13] Error applying inserts in bulk  :: caused by :: 151 Can't batch inserts into indexed capped collections trying first insert as a lone insert
      

      This also severely impacts performance since every batch insert throws and catches an exception.

      We should avoid trying to do vector inserts on capped collections. We can use the CachingCappedChecker for this, or some other clever technique.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: