Add a way to remember the opTime of where a config server data is based from. It will then be possible to add sanity checks in the server to make sure that it never tries to overwrite old data over a new one and also make sure that a collection opTime is always newer than the db opTime that owns it.
- is related to
-
SERVER-19855 Operations that convey shard version information must include a minimum optime
-
- Closed
-
-
SERVER-19390 Wire Read After Optime support into Replica Set Catalog Manager
-
- Closed
-