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

TransactionReaper should use something other than lastWriteOpTimeTs for staleness

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc2
    • Affects Version/s: 3.5.13
    • Component/s: None
    • None
    • Minor Change
    • ALL
    • Sharding 2017-10-23, Sharding 2017-11-13
    • 0

      The TransactionReaper mistakenly uses the time component of lastWriteOpTimeTs to notice transaction records over N minutes old (which we use to decide when transaction records are eligible for deletion due to a lack of a session record).

      We should flush an additional field to the transaction table which includes a wall clock time to compare against, as well as a redirecting the reaper to use that field for eligibility.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: