[ 
https://issues.apache.org/jira/browse/DRILL-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546367#comment-14546367
 ] 

Chris Westin commented on DRILL-3103:
-------------------------------------

>From the log file, it looks like the query was running, and one fragment
finished (2aa9c998-82d9-95d4-5b71-e310d5bf4d6a:frag:1:15), but then there
was a disconnection between the drillbit at 10.10.100.191 and
something else at 10.10.100.190:43360.

10.10.100.191: 2015-05-15 18:11:06,616 [UserServer-1] INFO  
o.a.drill.exec.rpc.user.UserServer - RPC connection /10.10.100.191:31010 <--> 
/10.10.100.190:43360 (user client) timed out.  Timeout was set to 30 seconds. 
Closing connection.
10.10.100.191: 2015-05-15 18:11:06,617 [UserServer-1] INFO  
o.a.d.e.w.fragment.FragmentExecutor - 2aa9c998-82d9-95d4-5b71-e310d5bf4d6a:0:0: 
State change requested from RUNNING --> FAILED for
10.10.100.191: 2015-05-15 18:11:06,618 [UserServer-1] INFO  
o.a.drill.exec.work.foreman.Foreman - State change requested.  RUNNING --> 
CANCELLATION_REQUESTED
10.10.100.191: 2015-05-15 18:11:06,631 [BitServer-4] INFO  
o.a.d.e.w.fragment.FragmentExecutor - 2aa9c998-82d9-95d4-5b71-e310d5bf4d6a:0:0: 
State change requested from FAILED --> CANCELLATION_REQUESTED for

It looks like the connection to the client timed out via
LogggingReadTimeoutHandler.


> EncoderException: RpcEncoder must produce at least one message.
> ---------------------------------------------------------------
>
>                 Key: DRILL-3103
>                 URL: https://issues.apache.org/jira/browse/DRILL-3103
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - RPC
>            Reporter: Rahul Challapalli
>            Assignee: Chris Westin
>         Attachments: error.log
>
>
> git.commit.id.abbrev=d8b1975
> I ran the below query on TPCH SF100 data on a 2 node cluster. The query 
> failed for some reason. I attached the logs
> Query
> {code}
> select o_orderkey from orders;
> {code}



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

Reply via email to