-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: 4.5.1
-
Component/s: Sharding
-
ALL
-
- Start a sharded cluster
- Shard a collection and move a chunk
- Restart a shard
- Cause an execution of the RSM
- Check that the sharded state of the collection is not unknown
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
In order to check the correct behavior of the change streams on recently restarted shards, it is needed to have a shard without initialized metadata. However, in some cases the restart can be seen as a topology change, which triggers the RSM thread, and this might lead to a refresh of the metadata. This generally causes failures when testing, because the exact scenario (a recently restarted shard) cannot be set. There should be a way to prevent this refresh, or, the way the change streams is tested should be changed.