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

Investigate performance for initial bulk loading in sharding

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Sharding NYC

    Description

      Currently in migration and resharding, we create the indexes first and then copy the documents. The indexes are then updated just like regular writes. Replication initial sync uses CollectionBulkLoaderImpl which defers index updates and then commits them manually with MultiIndexBlock at the end. This ticket is to investigate whether using the same strategy would net some performance improvements.

      Attachments

        Activity

          People

            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: