[
https://issues.apache.org/jira/browse/HIVE-23526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17113082#comment-17113082
]
Zhihua Deng edited comment on HIVE-23526 at 5/23/20, 8:02 AM:
--------------------------------------------------------------
The problem can be reproduced when there is not enough memory for thrift to
allocate the message, an oom error throws as a consequence, if the client now
issues ResultSet::close or HiveStatement::close in finally block, the response
returned should be the result of the last request, which causing out of
sequence response problem. As the beeline does not process the oom error
properly, only out of sequence shows at front.
was (Author: dengzh):
The problem can be reproduced when there is not enough memory for thrift to
allocate the message, an oom error throws as a consequence, if the client now
issues ResultSet#close or HiveStatement#close in finally block, the response
returned should be the result of the last request, which causing out of
sequence response problem. As the beeline does not process the oom error
properly, only out of sequence shows at front.
> Out of sequence seen in Beeline may swallow the real problem
> -------------------------------------------------------------
>
> Key: HIVE-23526
> URL: https://issues.apache.org/jira/browse/HIVE-23526
> Project: Hive
> Issue Type: Improvement
> Components: Beeline
> Environment: Hive 1.2.2
> Reporter: Zhihua Deng
> Assignee: Zhihua Deng
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-23526.2.patch, HIVE-23526.patch, outofsequence.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Sometimes we can see 'out of sequence response' message in beeline, for
> example:
> Error: org.apache.thrift.TApplicationException: CloseOperation failed: out of
> sequence response (state=08S01,code=0)
> java.sql.SQLException: org.apache.thrift.TApplicationException:
> CloseOperation failed: out of sequence response
> at
> org.apache.hive.jdbc.HiveStatement.closeClientOperation(HiveStatement.java:198)
> at org.apache.hive.jdbc.HiveStatement.close(HiveStatement.java:217)
> at org.apache.hive.beeline.Commands.execute(Commands.java:891)
> at org.apache.hive.beeline.Commands.sql(Commands.java:713)
> at org.apache.hive.beeline.BeeLine.dispatch(BeeLine.java:976)
> at org.apache.hive.beeline.BeeLine.execute(BeeLine.java:816)
> at org.apache.hive.beeline.BeeLine.begin(BeeLine.java:774)
> at org.apache.hive.beeline.BeeLine.mainWithInputRedirection(BeeLine.java:487)
> at org.apache.hive.beeline.BeeLine.main(BeeLine.java:470)
> and there is no other usage messages to figured it out, even with verbose
> flag, this makes problem puzzled as beeline does not have concurrency problem
> on underlying thrift transport.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
