-
Type: Documentation
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
2
-
Asparagus-StorEng - 2023-10-31
Any operation that could read a page into cache could return WT_CACHE_FULL due to timing out on cache_max_wait_ms.
While it's reasonable to expect cursor operations to return WT_CACHE_FULL, it's not clear if non-cursor operations - create, alter to name a few - may read a page into cache. We should clarify in the document which operations can return WT_CACHE_FULL.
- related to
-
SERVER-61116 Audit and add assertions against using multiple WT_SESSIONs on the same thread
- Backlog
-
WT-8767 Return rollback instead of cache full after cache_max_wait timer expires
- Closed