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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.6.6, 4.0.0-rc2, 4.1.1
    • Fix Version/s: 3.6.9, 4.0.4, 4.1.3
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0, v3.6
    • Sprint:
      Sharding 2018-08-27, Sharding 2018-09-10
    • Linked BF Score:
      68

      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

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: