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

Idempotency in cloning phase of initial sync

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication
    • Fully Compatible
    • ALL

    Description

      Since we copy the data from different snapshots and start building indexes before cloning data. The index spec may be inconsistent with the copied data, causing idempotency issues.

      Creat geo index
      --- start clone, get the geo index ---
      Drop the geo index
      Insert an invalid geo document
      --- copy the data, triggering geo parsing errors ----
      

      Relaxing index constraints in data cloning is one possible solution.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: