Details
-
Bug
-
Status: Backlog
-
Major - P3
-
Resolution: Unresolved
-
None
-
None
-
None
-
ALL
-
Description
If you set up a one-node replica set with the inMemory storage engine and continuously write data, eventually you will trigger eviction threads to spin hard at 100% cpu consumption.
Part of this bug is that oldest_timestamp is never updated, so the cache eventually fills with update data. However, whenever the cache fills, the inMemory storage engine should either start using a LAS file, or it should abort. (I don't think it will be logistically possible to block, as it would probably be a deadlock.)
Attachments
Issue Links
- related to
-
SERVER-29005 Review cache full handling for in-memory workloads
-
- Closed
-