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

Ensure that the CRUD events use the new shard key only after a reshardCollection event is generated

    XMLWordPrintableJSON

Details

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Execution

    Description

      Currently during the reshardCollection operation, the concurrent write operations on the collection being resharded can succeed during this phase execution. The distributed lock won't exclude new incoming writes on the collection. Since the change stream returns the events ordered on the clusterTime, there could be some writes which start using the new shard key value before logging the reshardCollection operation in the oplog. This would result in us reporting write events with new shard key value (as documentKey), before reporting the reshardCollection event.

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            arun.banala@mongodb.com Arun Banala
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: