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

change_streams_update_lookup_shard_metadata_missing.js should handle the node the change stream cursor was established on going through rollback

    • Fully Compatible
    • ALL
    • v4.4, v4.2, v4.0
    • Query 2020-06-01
    • 16

      The test establishes a change stream cursor, which establishes the cursor on all shard primaries. The test then causes a failover on one of the shards, then asserts that it is able to continue using the cursor.

      If the old shard primary goes through rollback as part of the failover (which happens nondeterministically since the test turns on the periodic noop writer on shards), all databases on that node will be closed and re-opened, which invalidates the change stream cursor and causes the test to fail when getMore is called on the cursor.

            bernard.gorman@mongodb.com Bernard Gorman
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            1 Vote for this issue
            3 Start watching this issue