-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Write Ops
-
None
-
Fully Compatible
-
v4.4
-
Repl 2019-11-18, Repl 2019-12-02, Repl 2020-03-23, Repl 2020-04-06
SERVER-42630 describes a case where an update entry will be written to the oplog as part of an applyOps but the actual performed operation may be an insert. This can be misleading or wrong for change streams. Currently change streams ignore user-generated applyOps entries but SERVER-42845 tracks the work to change that.
There are some comment threads on that ticket describing why, and judah.schvimer offers a proposed solution in this comment.
- is related to
-
SERVER-42630 Updates from user-executed "applyOps" can fail in initial sync
- Closed
-
SERVER-42845 Change streams should return events for user-initiated applyOps commands
- Closed
-
SERVER-21700 Do not relax constraints during steady state replication
- Closed
-
SERVER-33182 Remove atomic applyOps
- Closed
- related to
-
SERVER-47269 Add uses_change_streams tag to apply_ops_inserts_do_not_include_fromMigrate_field.js
- Closed
-
SERVER-46221 Remove oplogApplicationEnforcesSteadyStateConstraints parameter and opCounters
- Open
- split to
-
SERVER-45033 Log operations we do, not those we were told to do, in atomic applyOps oplog entries
- Closed