Different behavior on arm64 for invalid expireAfterSeconds value

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 4.4.15, 4.2.21
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Dan Larkin-York
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: