-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
v7.2, v7.0, v6.0, v5.0
-
Execution Team 2023-11-13, Execution Team 2023-11-27
-
(copied to CRM)
-
152
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The WTSizeStorer is used to keep fast counts for each collection in the system. Creating a collection adds an `ident` -> `count` mapping, but those key/value pairs are never deleted.
RTT makes this problem worse. When rolling forward from the stable point -> common point re-creates a collection, it will get a new `ident`, thus leaking the previous ident in the table.
- is depended on by
-
SERVER-82902 Dump size storer table in JSON format when testing that entries are removed
-
- Closed
-
-
SERVER-82903 Filter size storer entires using WT tool when testing that they are removed
-
- Closed
-
- is related to
-
SERVER-73757 Calling storageSize() on ephemeral temporary record stores returns 0
-
- Closed
-
-
SERVER-83120 Mechanism for one-time cleanup of orphaned size storer entries
-
- Closed
-
-
SERVER-83336 Temporarily disable wt_size_storer_cleanup_replica_set.js on macOS
-
- Closed
-