lastWriteDate field can get out of sync between repl set nodes during migration

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.6.9, 4.0.4, 4.1.3
    • Affects Version/s: 3.6.6, 4.0.0-rc2, 4.1.1
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Sharding 2018-08-27, Sharding 2018-09-10
    • 68
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Randolph Tan
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: