-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Aggregation Framework
-
Fully Compatible
-
ALL
-
v3.6
-
Repl 2017-11-13, Repl 2017-12-04
When using a change stream with fullDocument='updateLookup' against a sharded collection, the lookup will happen from mongos to the shards. This lookup should obey the read preference of the original command.
We should also use readConcern majority for this update, and use afterClusterTime to ensure we don't target to a secondary which is lagged behind the node that generated the change event.