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

change_streams_shards_start_in_sync.js should temporarily hang shard1 instead of rejecting cursor establishing request from mongos

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • v8.0
    • Cluster Scalability 2024-09-02
    • 0

      change_streams_shards_start_in_sync.js temporarily disconnects shard1 from the mongos so that it can test that change streams on sharded collections start in sync with each other. The issue with this is that this will cause the changestream to fail because when the mongos attempts to establish a cursor on shard1, it will get a HostUnreachable error. Instead of rejecting the cursor establishing request from the mongos, shard1 should temporarily hang. 

            Assignee:
            wenqin.ye@mongodb.com Wenqin Ye
            Reporter:
            wenqin.ye@mongodb.com Wenqin Ye
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: