-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
ALL
-
v8.0
-
Execution Team 2024-06-24, Execution Team 2024-07-08
-
200
InvalidTTLIndexFixer can find 'expireAfterSeconds' of type kNonInt when running on data generated from the newest version of mongod.
SERVER-77828 aimed to normalize expireAfterSeconds into an int on creation/collMod. The InvalidTTLIndexFixer runs on stepUp() to normalize any legacy data from older versions during upgrade.
We should investigate why it still finds kNonInt 'expireAfterSeconds' on non-legacy data.
- is related to
-
SERVER-91501 TTLMonitor can crash trying to deregister an already deregistered index
-
- Closed
-
- related to
-
SERVER-77828 listIndexes should report expireAfterSeconds as a float
-
- Closed
-
-
SERVER-80442 Remove logic to fix invalid expireAfterSeconds values post-creation
-
- Open
-