[ https://issues.apache.org/jira/browse/DRILL-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765065#comment-15765065 ]
Rahul Challapalli commented on DRILL-4708: ------------------------------------------ I was able to reproduce this error consistently in 3 out of 3 runs using the below query. The dataset is roughly 110GB. {code} [root@qa-node183 ~]# /opt/drill/bin/sqlline -n root -u jdbc:drill:zk=10.10.100.183:5181 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0 apache drill 1.10.0-SNAPSHOT "this isn't your grandfather's sql" 0: jdbc:drill:zk=10.10.100.183:5181> alter session set `planner.memory.max_query_memory_per_node` = 8589934592; +-------+----------------------------------------------------+ | ok | summary | +-------+----------------------------------------------------+ | true | planner.memory.max_query_memory_per_node updated. | +-------+----------------------------------------------------+ 1 row selected (0.34 seconds) 0: jdbc:drill:zk=10.10.100.183:5181> alter session set `planner.enable_decimal_data_type` = true; +-------+--------------------------------------------+ | ok | summary | +-------+--------------------------------------------+ | true | planner.enable_decimal_data_type updated. | +-------+--------------------------------------------+ 1 row selected (0.196 seconds) 0: jdbc:drill:zk=10.10.100.183:5181> select count(*) from (select * from dfs.`/drill/testdata/tpcds/parquet/sf1000/catalog_sales` order by cs_quantity, cs_wholesale_cost) d where d.cs_net_profit between 900.0 and 1000.0; Error: CONNECTION ERROR: Connection /10.10.100.183:57898 <--> qa-node183.qa.lab/10.10.100.183:31010 (user client) closed unexpectedly. Drillbit down? [Error Id: a8a83346-6b11-4d1a-a205-f120ba6c7ef0 ] (state=,code=0) {code} > connection closed unexpectedly > ------------------------------ > > Key: DRILL-4708 > URL: https://issues.apache.org/jira/browse/DRILL-4708 > Project: Apache Drill > Issue Type: Bug > Components: Execution - RPC > Affects Versions: 1.7.0 > Reporter: Chun Chang > > Running DRILL functional automation, we often see query failed randomly due > to the following unexpected connection close error. > {noformat} > Execution Failures: > /root/drillAutomation/framework/framework/resources/Functional/ctas/ctas_flatten/100000rows/filter5.q > Query: > select * from dfs.ctas_flatten.`filter5_100000rows_ctas` > Failed with exception > java.sql.SQLException: CONNECTION ERROR: Connection /10.10.100.171:36185 <--> > drillats4.qa.lab/10.10.100.174:31010 (user client) closed unexpectedly. > Drillbit down? > [Error Id: 3d5dad8e-80d0-4c7f-9012-013bf01ce2b7 ] > at > org.apache.drill.jdbc.impl.DrillCursor.nextRowInternally(DrillCursor.java:247) > at org.apache.drill.jdbc.impl.DrillCursor.next(DrillCursor.java:321) > at > oadd.net.hydromatic.avatica.AvaticaResultSet.next(AvaticaResultSet.java:187) > at > org.apache.drill.jdbc.impl.DrillResultSetImpl.next(DrillResultSetImpl.java:172) > at > org.apache.drill.test.framework.DrillTestJdbc.executeQuery(DrillTestJdbc.java:210) > at > org.apache.drill.test.framework.DrillTestJdbc.run(DrillTestJdbc.java:99) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: oadd.org.apache.drill.common.exceptions.UserException: CONNECTION > ERROR: Connection /10.10.100.171:36185 <--> > drillats4.qa.lab/10.10.100.174:31010 (user client) closed unexpectedly. > Drillbit down? > [Error Id: 3d5dad8e-80d0-4c7f-9012-013bf01ce2b7 ] > at > oadd.org.apache.drill.common.exceptions.UserException$Builder.build(UserException.java:543) > at > oadd.org.apache.drill.exec.rpc.user.QueryResultHandler$ChannelClosedHandler$1.operationComplete(QueryResultHandler.java:373) > at > oadd.io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:680) > at > oadd.io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:603) > at > oadd.io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:563) > at > oadd.io.netty.util.concurrent.DefaultPromise.trySuccess(DefaultPromise.java:406) > at > oadd.io.netty.channel.DefaultChannelPromise.trySuccess(DefaultChannelPromise.java:82) > at > oadd.io.netty.channel.AbstractChannel$CloseFuture.setClosed(AbstractChannel.java:943) > at > oadd.io.netty.channel.AbstractChannel$AbstractUnsafe.doClose0(AbstractChannel.java:592) > at > oadd.io.netty.channel.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:584) > at > oadd.io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.closeOnRead(AbstractNioByteChannel.java:71) > at > oadd.io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.handleReadException(AbstractNioByteChannel.java:89) > at > oadd.io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:162) > at > oadd.io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511) > at > oadd.io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468) > at > oadd.io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382) > at oadd.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354) > at > oadd.io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111) > ... 1 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)