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

Investigate rescanning an index vs processing concurrent writes after interrupt during unique index conversion

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution

    Description

      In the implementation for SERVER-61486, interrupting the unique index collMod request will stop tracking concurrent writes. It's possible that it would be more work to process all the concurrent writes than the rescan the index based on how much concurrent activity there is.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            pavithra.vetriselvan@mongodb.com Pavithra Vetriselvan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: