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

Different behavior on arm64 for invalid expireAfterSeconds value

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 4.4.15, 4.2.21
    • None
    • None
    • Storage Execution
    • ALL

    Description

      If a user creates a TTL index with {expireAfterSeconds: NaN}, an x86_64 server will throw an exception when trying to process documents in the TTL deleter, while an arm64 server will interpret the NaN as a 0 and proceed to delete all documents from the collection.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            dan.larkin-york@mongodb.com Dan Larkin-York
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: