We have a set of Impala UDFs that are packaged into a jar and deployed to HDFS. The UDFs work fine most of the time but occasionally we'll get an error: java.sql.SQLException: [Simba] [ImpalaJDBCDriver] (500051) ERROR processing query/statement. Error Code: ERROR_STATE, SQL state: ImpalaRuntimeException: Unable to find class.<br/>CAUSED BY: ClassNotFoundException: com.adaptive.analyzer.impala.IDToPartitionKey<br/> , Once the error occurs it throws anytime the UDF is used. The only way we've found to recover is to drop the function and restart impalad across all coordinator and executor nodes. Groveling through the Impala logs hasn't turned up anything useful. This first occurred on impala 2.8 but we continued to see it on 2.14 and 3.2. Any help would be appreciated.
... View more
We recently upgraded Impala from 2.14 to 3.2. The same code that was running against 2.14 is now running into Connection timeout errors with lots of open sessions shown in the coordinator node Web UI. We added idle-session-timeout to impalad startup in hopes that would clean out idle sessions but it only seems to mark them as expired but does not close them. After a couple hours of moderate use of our system attempts to make JDBC connections start timing out. Closing the idle sessions manually through the Web UI doesn't seem to solve the problem. Only a restart of the coordinator nodes seems to allow the client to create connections again. We have upgraded the JDBC driver to ClouderaIimpalaJDBC41-220.127.116.113 hoping that would help fix the issue but it doesn't seem to have improved any. Any help is appreciated.
... View more