Adding to what @ChethanYM said, shared traces can also arise from third party tool while connection gets closed abruptly or issue with proxy host/knox if you are using one in JDBC connection settings. If you would like more debugging on this, appending JDBC driver DEBUG logs would be helpful. To do so, add below with JDBC connection string and repro the issue , It will generate driver DEBUG logs and may give some more details about the issue. LogLevel=6;LogPath=/tmp/jdbclog Regards, Krish ... View more

@hadoopranger  Consider tuning parameters like idle_session_timeout and idle_query_timeout which is suspected to be closing the session considering you don't have LB in place. You can also set it to 0 where session will never expire until closed manually. Moreover, consider increasing value of fe_service_threads to allow more concurrent client connections which should help you avoiding similar client connection issue in future. For more info, refer: https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/impala-reference/topics/impala-recommended-configs.html ... View more

@michalwojtowicz Mentioned error seem to be complaining about expired session which either gets terminated by client or server. Now, to answer your question driver config has SocketTimeout which controls TCP connection: "The number of seconds that the TCP socket waits for a response from the server before raising an error on the request." and default value of the same is 0(i.e the connection does not time out.) Refer: https://docs.cloudera.com/documentation/other/connectors/impala-jdbc/2-6-34/Cloudera-JDBC-Connector-for-Apache-Impala-Install-Guide.pdf However, could you confirm whether you have loadbalancer in place for impala through which you are connecting using JDBC driver? If yes, consider reviewing LB settings which should have timeout configurations allowing server to close the connection for long running queries, for instance: === timeout connect timeout client timeout server === ... View more

I believe there is a better way to do it from hue config than changing the python code: > Navigate to HUE > Configuration > Hue Service Advanced Configuration Snippet (Safety Valve) for hue_safety_valve.ini > add == [beeswax] max_catalog_sql_entries=15000 == If you need to list 15000 entries at once instead of 5k which is by default. > Save and restart affected Note that, you can't expect optimal performance out of HUE UI to load table list since no is too high and this is not a hue limitation rather being put on purpose so that table list load can be faster. ... View more