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

Remove the usage of distributed collection lock during map/reduce

    XMLWordPrintableJSON

Details

    • Sharding

    Description

      Map/reduce with a sharded output collection performs an optimization where the final reduce step is omitted and the previous reduce step is done in parallel on all shards. This is done by creating an empty sharded collection and spreading the chunks so they are co-located with the data to be reduced based on the shard key, writing all output locally to an empty temporary collection and then renaming the temporary collection to the name of the output collection.

      This process only works if no chunks of the output collection move around while the output is being written and is protected through the usage of the collection distributed lock.

      This task is to get rid of this reliance on the collection distributed lock.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: