During the 3.2->3.4 upgrade process there can exist a period of time where the shards are all v3.4, but the config server has yet to upsert a shardIdentity docuument on to the shards. We should verify that nothing goes wrong in that situation by writing a jstest that performs a variety of operations (CRUD, aggregate, mapReduce, findAndModify, distinct, count, group, etc) against a sharded cluster setup without shardIdentity documents.
- related to
-
SERVER-24527 add test to ensure shard undergoes sharding initialization through setShardVersion
-
- Closed
-
-
SERVER-26083 create library of basic ops that can be run against a cluster under different conditions
-
- Closed
-