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

When cloning capped collection during initial sync cap the number of cloned objects to size of collection

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • 2.4.8, 2.5.4
    • Replication
    • None
    • Replication

    Description

      Currently if initial sync starts cloning a capped collection that's being written to at a comparable rate to sync rate, it's possible for the sync to go on far longer than it should, and in some cases its cursor can get invalidated by newer inserts which are triggering 'deleteRecord' from 'cappedAlloc' which on capped collection are invalidating the cursor.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            asya.kamsky@mongodb.com Asya Kamsky
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: