You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Deneche A. Hakim (JIRA)" <ji...@apache.org> on 2016/05/17 21:37:13 UTC
[jira] [Commented] (DRILL-4681) ChannelClosedException causes all
queries which are communicating on that channel to fail
[ https://issues.apache.org/jira/browse/DRILL-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287630#comment-15287630 ]
Deneche A. Hakim commented on DRILL-4681:
-----------------------------------------
[~rkins] can you explain what you mean by "even though the fragments themselves eventually run to completion" ?
My understanding is that Drill will fail all fragments that were sending batches through the closed channel and didn't yet receive an ACK, so those batches are assumed to be lost.
> ChannelClosedException causes all queries which are communicating on that channel to fail
> ------------------------------------------------------------------------------------------
>
> Key: DRILL-4681
> URL: https://issues.apache.org/jira/browse/DRILL-4681
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow, Execution - RPC
> Affects Versions: 1.7.0
> Reporter: Rahul Challapalli
>
> commit # : 09b262776e965ea17a6a863801f7e1ee3e5b3d5a
> Below is what I am describing:
> 1. One of the fragments cause a channel closed exception (due to an OOM or some other condition)
> 2. Drill fails all other fragments which are running at that time even though the fragments themselves eventually run to completion. At a high concurrency this could lead a lot of query failures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)