Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-35763

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

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 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
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v4.0, v3.6
    • Sharding 2018-08-27, Sharding 2018-09-10
    • 68

      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@mongodb.com Randolph Tan
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: