From issues-return-191622-apmail-hive-issues-archive=hive.apache.org@hive.apache.org Mon Jun 1 06:08:03 2020 Return-Path: X-Original-To: apmail-hive-issues-archive@minotaur.apache.org Delivered-To: apmail-hive-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by minotaur.apache.org (Postfix) with SMTP id 0D91919DF4 for ; Mon, 1 Jun 2020 06:08:02 +0000 (UTC) Received: (qmail 18079 invoked by uid 500); 1 Jun 2020 06:08:02 -0000 Delivered-To: apmail-hive-issues-archive@hive.apache.org Received: (qmail 18052 invoked by uid 500); 1 Jun 2020 06:08:02 -0000 Mailing-List: contact issues-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list issues@hive.apache.org Received: (qmail 18043 invoked by uid 99); 1 Jun 2020 06:08:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jun 2020 06:08:02 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 479F3E05CD for ; Mon, 1 Jun 2020 06:08:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 04ECD78014A for ; Mon, 1 Jun 2020 06:08:00 +0000 (UTC) Date: Mon, 1 Jun 2020 06:08:00 +0000 (UTC) From: "Zhihua Deng (Jira)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (HIVE-23526) Beeline may throw the misleading exception MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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 6/1/20, 6:07 AM: ------------------------------------------------------------- The problem can be reproduced when there is not enough memory for thrift to allocate the message or unsuccessfully read response from server(Read timeout) , if the client now issues ResultSet::close or HiveStatement::close in finally block, the client may get the result of the last request, which causing out of sequence response problem. As beeline does not process the root cause 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. > Beeline may throw the misleading exception > ------------------------------------------ > > Key: HIVE-23526 > URL: https://issues.apache.org/jira/browse/HIVE-23526 > Project: Hive > Issue Type: Bug > Components: Beeline > Environment: Hive 1.2.2 > Reporter: Zhihua Deng > Priority: Major > Labels: pull-request-available > Attachments: HIVE-23526.2.patch, HIVE-23526.3.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 message to figured it out, even with --verbose, 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)