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

Session::onMigrateCompletedOnPrimary should not update the lastWriteDate field

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.6, 4.0.0-rc2, 4.1.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • v4.0, v3.6
    • Sharding 2018-05-21, Sharding 2018-06-04

      It currently overwrites the latest transaction's lastWriteDate with that from the oplog being migrated and thus it can move the lastWriteDate back. This could cause sessions to be cleaned earlier than the actual last time they were written to.

      Instead, it should just keep the value as is since migrations don't really modify the state of the config.transactions from the point of view of a sharded cluster.

            Assignee:
            blake.oler@mongodb.com Blake Oler
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: