Return-Path: 
 <issues-return-25092-apmail-drill-issues-archive=drill.apache.org@drill.apache.org>
X-Original-To: apmail-drill-issues-archive@minotaur.apache.org
Delivered-To: apmail-drill-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 4A64918C40
	for <apmail-drill-issues-archive@minotaur.apache.org>;
 Mon, 19 Oct 2015 09:04:05 +0000 (UTC)
Received: (qmail 1673 invoked by uid 500); 19 Oct 2015 09:04:05 -0000
Delivered-To: apmail-drill-issues-archive@drill.apache.org
Received: (qmail 1645 invoked by uid 500); 19 Oct 2015 09:04:05 -0000
Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@drill.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@drill.apache.org>
List-Post: <mailto:issues@drill.apache.org>
List-Id: <issues.drill.apache.org>
Reply-To: dev@drill.apache.org
Delivered-To: mailing list issues@drill.apache.org
Received: (qmail 1622 invoked by uid 99); 19 Oct 2015 09:04:05 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Oct 2015 09:04:05 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 107382C033A
	for <issues@drill.apache.org>; Mon, 19 Oct 2015 09:04:05 +0000 (UTC)
Date: Mon, 19 Oct 2015 09:04:05 +0000 (UTC)
From: "Yiyi Hu (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12895751.1443006732000.72777.1445245445063@Atlassian.JIRA>
In-Reply-To: <JIRA.12895751.1443006732000@Atlassian.JIRA>
References: <JIRA.12895751.1443006732000@Atlassian.JIRA>
 <JIRA.12895751.1443006732275@arcas>
Subject: [jira] [Updated] (DRILL-3826) Concurrent Query Submission leads to
 Channel Closed 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/DRILL-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yiyi Hu updated DRILL-3826:
---------------------------
    Attachment:     (was: Sample2.png)

> Concurrent Query Submission leads to Channel Closed Exception
> -------------------------------------------------------------
>
>                 Key: DRILL-3826
>                 URL: https://issues.apache.org/jira/browse/DRILL-3826
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC, Execution - RPC
>    Affects Versions: 1.1.0, 1.2.0
>         Environment: - CentOS release 6.6 (Final)
> - hadoop-2.7.1
> - hbase-1.0.1.1
> - drill-1.1.0
> - jdk-1.8.0_45
>            Reporter: Yiyi Hu
>            Assignee: Daniel Barclay (Drill)
>              Labels: filesystem, hadoop, hbase, jdbc, rpc
>             Fix For: Future
>
>         Attachments: jdbc-test-client-drillbit.log, shell-sqlline.log, shell-test-drillbit.log
>
>
> Frequently seen CHANNEL CLOSED EXCEPTION while running concurrent quries with relatively large LIMIT.
> Here are the details,
> SET UP:
> - Single drillbit running on a single zookeeper node
> - 4G heap size, 8G direct memory
> - Storage plugins: local filesystem, hdfs, hbase
> TEST DATA:
> - A 50,000,000 records json file test.json, with two fields id<Int>, title<String>  (approximately 3G).
> SHELL TEST:
> - Running 4 drill shells concurrently with query:
>   SELECT id, title from dfs.`test.json` LIMIT 5000000.
> - Queries got canceled. Channel closing between client and server were seen randomly, as an example shown below:
> {noformat}
> java.lang.RuntimeException: java.sql.SQLException: SYSTEM ERROR: ChannelClosedException: Channel closed /192.168.4.201:31010 <--> /192.168.4.201:48829.
> Fragment 0:0
> [Error Id: 0bd2b500-155e-46e0-9f26-bd89fea47a25 on TEST-101:31010]
> 	at sqlline.IncrementalRows.hasNext(IncrementalRows.java:73)
> 	at sqlline.TableOutputFormat$ResizingRowsProvider.next(TableOutputFormat.java:87)
> 	at sqlline.TableOutputFormat.print(TableOutputFormat.java:118)
> 	at sqlline.SqlLine.print(SqlLine.java:1583)
> 	at sqlline.Commands.execute(Commands.java:852)
> 	at sqlline.Commands.sql(Commands.java:751)
> 	at sqlline.SqlLine.dispatch(SqlLine.java:738)
> 	at sqlline.SqlLine.begin(SqlLine.java:612)
> 	at sqlline.SqlLine.start(SqlLine.java:366)
> 	at sqlline.SqlLine.main(SqlLine.java:259)
> {noformat}
> JDBC TEST:
> - 6 separate threads running the same query: SELECT id, title from dfs.`test.json` LIMIT 10000000, each maintains its own connection. ResultSet, statement and connection are closed finally.
> - Throws the same channel closed exception randomly. Log file were enclosed for review.
> - Memory usage was monitored, all good.
> CROSS STORAGE PLUGINS:
> - The same issue can be found not only in JSON on a file system (local/hdfs), but also in HBASE.
> - The issue was not found in a single thread application.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)