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

Move cluster topology change notifications out of the change stream pipeline

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.1.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • v5.0
    • Query Execution 2021-05-17, Query Execution 2021-05-31

    Description

      Currently, when a collection migrates to a new shard, an event is generated that passes through the pipeline to the mongoS, where it is consumed by the DocumentSourceUpdateOnAddShard stage. But when we start pushing down user-defined $match filters to the shard, we can no longer guarantee that the event will make it as far as DSUOAS, and migration events may therefore be missed.

      We should move our handling of the kNewShardDetected event out of the change stream pipeline.

      Attachments

        Activity

          People

            rishab.joshi@mongodb.com Rishab Joshi (Inactive)
            bernard.gorman@mongodb.com Bernard Gorman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: