Hello. I'm working with a two nodes Exasol 6.2 installation, used as data source for Tableau dashboards. We're trying to optimize the connection between Exasol and Tableau looking for potential bottlenecks.
After having read the Session Management page, I had a look at the Exasol logs:
Another Community post adresses the same topic, but it doesn't provide a clear solution.
I would like to modify the maximum number of connections. The EXA_METADATA table contains these values:
Which one should I modify? And above all, how can I modify it? Being database parameters, I doubt a simple UPDATE would be enough.
By the way, where can I find a thorough explanation of the EXA_METADATA table values? The documentation isn't very extensive.
Thank you in advance.
Hello everyone. I'm back discussing this issue because I feel as it has become a personal challenge... En garde!
Jokes aside, I'm really interested in it and I would like to have a better understanding on how Exasol works.
The Session Management page states:
A session is defined as active if it matches at least one of the following conditions:
Each active session occupies one active slot.
Currently, there is no way to find out the Connected states through system tables. Connected, inactive and Disconnected sessions should have a TEMP_DB_RAM_USAGE of 0.0 in the current session list.
If I correctly understand it, in fair approximation I could estimate the number of Connected, active sessions in a given moment having a look at the EXA_DBA_AUDIT_SESSIONS table and filtering by TEMP_DB_RAM_USAGE > 0. Right?
Changing parameters should only be done on the recommendation of Exasol support.
It is usually more worthwhile to investigate why you are getting close than to increase the limit.
There is also a known bug regarding the display of that error message in Exaoperation (https://www.exasol.com/support/browse/EXASOL-2724), but if you are actually hitting the limit very regularly, we can take a look at it.
Hitting the warning trigger does not have any impact for users or queries - it's just an FYI in Exaoperation to make you aware of it.
Hi @ecoh_dr ,
setting different parameters would require a restart of your DB instance - also, normally you shouldn´t "play" with those setting, at least not without talking it through with exa support ( or on an expandable test environment 😉 ).
Regarding more than 100 ACTIVE sessions: bear in mind that each session would ( under standard resource management conditions ) receive only 1/100 of your systems performance/resources - I don´t think you´d want that.
Why do you have that many ACTIVE sessions in parallel ? Is that a tableu thing ? As Exa mentions on occasion, they are query throughput optimized, so any given query should finish rather quickly and the system should not be "bogged down" with lots and lots of concurrent ACTIVE sessions.
Maybe some details on how this "session bonanza" gets created ?