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

Session::onMigrateCompletedOnPrimary should not update the lastWriteDate field

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.6, 4.0.0-rc2, 4.1.1
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0, v3.6
    • Sprint:
      Sharding 2018-05-21, Sharding 2018-06-04

      Description

      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.

        Attachments

          Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35763 lastWriteDate field can get out of sync between repl set nodes during migration

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              blake.oler Blake Oler
              Reporter:
              renctan Randolph Tan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: