-
Type: Improvement
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
Storage 2017-08-21
Currently, when we hit the WT session limit, we log the following message:
WT_CONNECTION.open_session: only configured to support 20020 sessions (including 20 additional internal sessions): Cannot allocate memory
However, this is misleading since we can hit the WT session limits when there is plenty of available memory.
We should log instead:
WT_CONNECTION.open_session: only configured to support 20020 sessions (including 20 additional internal sessions): Cannot allocate *resource*