[SOL-296] Session management in EXASolution Created: 28.07.2015 Updated: 14.11.2019 Resolved: 14.11.2019
|Affects Version/s:||EXASolution 5.0, EXASOL 6.0.0, Exasol 6.1.0|
|Reporter:||Captain EXASOL||Assignee:||Captain EXASOL|
Note: This solution is no longer maintained. For the latest information, please refer to our documentation:
EXASolution is able to handle 10.000 sessions per node. These sessions can be either active or inactive.
Each active session occupies one active slot. The number of the active slots is limited per default to 100 (globally, not per node). In inactive to active transition the session may wait for active slot to becomes available. In such case the status QUEUED will be shown for all waiting sessions in the STATUS column of EXA_*SESSIONS. All waiting for _active slot sessions are served in FIFO manner.
Since EXASolution 5.0.11 there are 100 additional active but blocked session slots available for sessions that are waiting for another session. Typically they are waiting for commit and have status "Waiting for session" in the ACTIVITY column of EXA_*_SESSIONS. If the number of the blocked sessions exceeds the
Since EXASolution 5.0.12 an EXAoperation warning is generated if 80% of the maximum allowed active session slots are in use:
If a login request can't be processed and has to wait because no free active session slots are available, an EXAoperation warning will be periodically logged until all requests have been processed:
|Category 1:||Database Administration|
|Category 2:||Clients, Interfaces & Drivers|