-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Server Serverless 2022-04-18
-
172
The problem is that when we compared the oldConfig vs the newConfig in the replication_coordinator, the newConfig is constructed from the MutableReplSetConfig which removes the data for `recipientConfig`.
So eventually when we compare the old vs new config, the new config no longer holds the recipientConfig and the comparison fails.
We should ensure that the `recipientConfig` is always set if it was previously present on the object it is constructed from.