anchor.diff:  In this case, when the connector configured with _initial_ snapshot mode (the default) is finally restarted, the MongoDB server will no longer have the starting point and the connector will fail with an error.
   ====
   
  +[id="mongodb-crash-results-in-lost-commits"]
   === MongoDB loses writes
   
  -It is possible for MongoDB to lose commits in specific failure situations. For example, if the primary applies a change and records it in its oplog before it then crashes unexpectedly, the secondary nodes may not have had a chance to read those changes from the primary's oplog before the primary crashed. If one such secondary is then elected as primary, its oplog is missing the last changes that the old primary had recorded and no longer has those changes.
  -
  -In these cases where MongoDB loses changes recorded in a primary's oplog, it is possible that the MongoDB connector may or may not capture these lost changes. At this time, there is no way to prevent this side effect of MongoDB.
  +In certain failure situations, MongoDB can lose commits, which results in the MongoDB connector being unable to capture the lost changes.
  +For example, if the primary crashes suddenly after it applies a change and records the change to its oplog, the oplog might become unavailable before secondary nodes can read its contents.
  +As a result, the secondary node that is elected as the new primary node might be missing the most recent changes from its oplog.
  +
  +At this time, there is no way to prevent this side effect in MongoDB.
  
positive.code: 
  If the group contains only one process and that process is stopped gracefully, then Kafka Connect will stop the connector and record the last offset for each replica set. Upon restart, the replica set tasks will continue exactly where they left off.
  
  === Kafka Connect process crashes
  
  If the Kafka Connector process stops unexpectedly, then any connector tasks it was running will terminate without recording their most recently-processed offsets.
  
negative.code: ====
  
  [id="mongodb-delete-events"]
  === _delete_ events
  
  The value in a _delete_ change event has the same `schema` portion as _create_ and _update_ events for the same collection. The `payload` portion in a _delete_ event contains values that are different from _create_ and _update_ events for the same collection. In particular, a _delete_ event contains neither an `after` value nor a `patch` value. Here is an example of a _delete_ event for a document in the `customers` collection:
  
  