[SERVER-68283] Different behavior on arm64 for invalid expireAfterSeconds value Created: 25/Jul/22  Updated: 05/Dec/22  Resolved: 25/Jul/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.4.15, 4.2.21
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Backlog - Storage Execution Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-56676 improve handling of large/NaN values ... Closed
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 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.


Generated at Thu Feb 08 06:10:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.