Due to capped collections performing their own deletes on different nodes in a replica set asynchronously before 5.0, data can diverge and later operations might "violate" replication constraints for inserts, updates, and deletes. We log these violations for inserts and delete, but we skip it for updates.

Since these violations are actually harmless and self-correcting, we would want to separate them from other types of constraint violations. We should also log this for updates.