-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Fully Compatible
-
ALL
-
Sharding EMEA 2022-10-03
-
6
Rather than having a FSM state that verifies that all performed operations are seen at the level of change streams, we should do it just once, at the very end.
Note that other approaches like trying to reduce the NoopIntervalPeriodicSeconds doesn't work: this parameter can only be changed at STARTUP, so in the context of a FSM we are not able to modify it.
We might need to backport this fix to 6.0.