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

Prevent TTLMonitor from processing index if expireAfterSeconds is NaN

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.2.23, 4.4.16
    • None
    • None
    • Fully Compatible
    • ALL
    • v6.0, v5.0, v4.4, v4.2
    • Execution Team 2022-08-08

    Description

      The TTLMonitor is responsible for removing expired documents from a collection with a TTL index. The expireAfterSeconds option is a numerical value that is used to calculate the expiration time for removing documents.

      In 5.0 (see SERVER-56676), the TTL Monitor was updated to handle values that fall outside the long long range. However, because BSONElement::safeNumberLong() returns 0 for NaN values, SERVER-56676 sets the TTL expiration so that documents are expired immediately.

      In versions before 5.0, the handling of NaN values for the expireAfterSeconds field is platform-dependent.

      Attachments

        Issue Links

          Activity

            People

              benety.goh@mongodb.com Benety Goh
              benety.goh@mongodb.com Benety Goh
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: