question Re: Impala query error in Support Questions

Impala query error

ysong26 — Fri, 07 Feb 2025 04:57:35 GMT

Please note that the previous text was translated using a translator, so it might sound a bit awkward. I apologize for any confusion.

I’m encountering an issue where everything runs fine initially, but sometimes I experience this error. Could anyone help me understand what might be causing it?

[Cloudera][ImpalaJDBCDriver](500051) ERROR processing query/statement. Error Code: ExecuteStatement failed: out of sequence response: expected 6 but got 5, SQL state: HY000,

Query: select * from (SELECT tool_path,tag,act_time,value,row_number() over (partition by tool_path,tag order by act_time desc) as rownum FROM `X`.`Y` WHERE (tag like 'A%' or tag like 'B%' or tag like 'C%' or tag like 'D%' or tag like 'E%' or tag like 'F%' or tag like 'G%' or tag like 'H%' or tag like 'I%' or tag like 'J%' or tag like 'K%' or tag like 'L%' or tag like 'M%' or tag like 'N%' or tag like 'O%' or tag like 'P%' or tag like 'Q%' or tag like 'R%' or tag like 'S%' or tag like 'T%' or tag like 'U%') and act_time BETWEEN DATE_SUB(NOW(), INTERVAL 2 HOUR) AND NOW() and param_type = 'M') a where rownum=1.

Re: Impala query error

VidyaSargur — Fri, 07 Feb 2025 07:04:01 GMT

@ysong26,Welcome to our community! To help you get the best possible answer, I have tagged our Impala experts @ChethanYM @willx who may be able to assist you further.

Please feel free to provide any additional information or details about your query, and we hope that you will find a satisfactory solution to your question.

Re: Impala query error

ChethanYM — Thu, 13 Feb 2025 13:33:33 GMT

@ysong26 The "out of sequence response" error suggests that the Impala JDBC driver expected a specific response sequence but received an unexpected one.

This can happen due to network latency, dropped packets, or an issue in the client-server communication.

See if you have set high value for "defaultRowBatchSize" property, If yes you can lower it and check which JDBC driver version you are using try to use the latest version available and see if that helps.

Also verify if any network issues in the system.

Regards,

Chethan YM

Re: Impala query error

VidyaSargur — Thu, 27 Feb 2025 10:49:36 GMT

@ysong26 Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future.

Re: Impala query error

kbanik — Wed, 02 Apr 2025 20:44:20 GMT

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