Details
Description
The issue is that during migration, we might decide to not update the lastWriteDate. However, the secondary replication doesn't have this logic and it will simply use the oplog wall time to set the lastWriteDate field.
Attachments
Issue Links
- is related to
-
SERVER-33327 Session::onMigrateCompletedOnPrimary should not update the lastWriteDate field
-
- Closed
-