This property is a startup option (boot option) which can be set in 
drill-override.conf ($DRILL_HOME/conf).You can specify it as highlighted below.

drill.exec: {
  cluster-id: "<cluster id>",
  zk.connect: "<zk_server:port>",
  rpc.user.timeout :60

}

Restart Drill service once changes are made in all drillbit nodes. You can 
verify the value set using below SQL.

select * from sys.boot where name = 'drill.exec.rpc.user.timeout';

The options tab in Web UI lists system options which can be set at 
system/session level.


https://drill.apache.org/docs/start-up-options/


https://drill.apache.org/docs/configuration-options-introduction/



Thanks,

Arjun

________________________________
From: Divya Gehlot <divya.htco...@gmail.com>
Sent: Friday, November 3, 2017 11:51 AM
To: user@drill.apache.org
Subject: Re: Apache Drill connection issue in tableau

Hi Timothy,
Thanks for the help!
Yes you are right I could see below error message in the logs
Where can I set the rpc time out as I couldnt find the rpc timeout config
in when login through web console -> Options
Could you please help me pointing it ?

2017-11-03 04:48:30,413 [BitServer-4] INFO
o.a.drill.exec.work.foreman.Foreman - Failure while trying communicate
query result to initiating client. This would happen if a client is
disconnected before response notice can be sent.
org.apache.drill.exec.rpc.RpcException: Failure sending message.
        at org.apache.drill.exec.rpc.RpcBus.send(RpcBus.java:124)
[drill-rpc-1.10.0.jar:1.10.0]
        at 
org.apache.drill.exec.rpc.user.UserServer$BitToUserConnection.sendResult(UserServer.java:199)
[drill-java-exec-1.10.0.jar:1.10.0]
        at 
org.apache.drill.exec.work.foreman.Foreman$ForemanResult.close(Foreman.java:868)
[drill-java-exec-1.10.0.jar:1.10.0]
        at 
org.apache.drill.exec.work.foreman.Foreman.moveToState(Foreman.java:1001)
[drill-java-exec-1.10.0.jar:1.10.0]
        at 
org.apache.drill.exec.work.foreman.Foreman.access$2600(Foreman.java:116)
[drill-java-exec-1.10.0.jar:1.10.0]
        at 
org.apache.drill.exec.work.foreman.Foreman$StateSwitch.processEvent(Foreman.java:1027)
[drill-java-exec-1.10.0.jar:1.10.0]
        at 
org.apache.drill.exec.work.foreman.Foreman$StateSwitch.processEvent(Foreman.java:1020)
[drill-java-exec-1.10.0.jar:1.10.0]
        at 
org.apache.drill.common.EventProcessor.processEvents(EventProcessor.java:107)
[drill-common-1.10.0.jar:1.10.0]
        at 
org.apache.drill.common.EventProcessor.sendEvent(EventProcessor.java:65)
[drill-common-1.10.0.jar:1.10.0]
        at 
org.apache.drill.exec.work.foreman.Foreman$StateSwitch.addEvent(Foreman.java:1022)
[drill-java-exec-1.10.0.jar:1.10.0]
        at 
org.apache.drill.exec.work.foreman.Foreman.addToEventQueue(Foreman.java:1040)
[drill-java-exec-1.10.0.jar:1.10.0]
        at 
org.apache.drill.exec.work.foreman.QueryManager.nodeComplete(QueryManager.java:506)
[drill-java-exec-1.10.0.jar:1.10.0]


Thanks,
Divya

On 1 November 2017 at 01:08, Timothy Farkas <tfar...@mapr.com> wrote:

> Can you share the logs from your Drill bit? Without the logs I'm taking a
> shot in the dark but
>
> you can try increasing the timeout between the DrillClient and foreman by
> adding this configuration
>
> to your drill-override.conf
>
>
>
> drill.exec.rpc.user.timeout: 30
>
> Thanks,
> Tim
>
>
> ________________________________
> From: Divya Gehlot <divya.htco...@gmail.com>
> Sent: Tuesday, October 31, 2017 12:26:55 AM
> To: user@drill.apache.org
> Subject: Apache Drill connection issue in tableau
>
> Hi ,
> I am facing  a strange Drill connection issue.
> I am connecting to Drill through Tableau.
> I have published coupled of reports to tableau server.
> When I connect to Drill thorugh tableau desktop and tableau server at same
> time
> it becomes unresponding.I keeping getting "connection time out error" or in
> tableau "connection to port is lost" .
> But when I close the tableau desktop and just connected to published
> reports to tableau server everything works fine and no time out error.
>
> Not sure if I need to update any drill configurations ?
>
> Appreciate the help !
>
> Thanks,
> Divya
>

Reply via email to