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.
- is caused by
-
SERVER-78115 Shard primaries must commit a majority write before using new routing information from the config server
- Closed