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

Change streams can output events in a different order for multi shard transactions

    XMLWordPrintableJSON

Details

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

    Description

      Changestreams orders events from txn by the clusterTime of the commitTransaction. But the order of when commit transaction occurs in shard is orthogonal to the order of when individual ops where issued. For example, in the case of changing the shard key of a document. This will involve deleting document on shardA and inserting the document with the new shard key on shardB under a single transaction. It is possible that commit can happen on shardB first, resulting in the change streams showing the insert first instead of the delete.

      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: