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

Avoid leaving the replica set shard partitioned at the end of `linearizable_read_concern.js`

    • Sharding EMEA
    • Fully Compatible
    • ALL
    • v7.1, v7.0, v6.0, v5.0
    • Sharding EMEA 2023-09-18
    • 40

      This test sets up a sharded cluster and at the end leaves the secondary nodes of a shard disconnected from the primary. The metadata consistency check is triggered by default when the sharded cluster terminates, causing a WriteConcernFailed error.

      This problem is expected when the filtering metadata is refreshed (due to a majority-write in the catalog cache) as a consequence of the metadata consistency check.

      The goal of this ticket is to reconnect the secondary nodes at the end of the test, and also enable all consistency checks that are explicitly disabled.

            antonio.fuschetto@mongodb.com Antonio Fuschetto
            antonio.fuschetto@mongodb.com Antonio Fuschetto
            0 Vote for this issue
            2 Start watching this issue