You may want to log the ODBC driver. Which version of the ODBC driver are you using?
Are you using Windows or OSX? For windows edit the registry entry HKEY_LOCAL_MACHINE/SOFTWARE/MapR/MapR Drill ODBC Driver/Driver On OSX copy file mapr.drillodbc.ini in /Library/mapr/drill/Setup/ to /Library/mapr/drill/lib Set the log level and location in the above for either OS. Log levels 0 Disables all logging. 1 Logs severe error events that lead the driver to abort. 2 Logs error events that might allow the driver to continue running. 3 Logs events that might result in an error if action is not taken. 4 Logs general information that describes the progress of the driver. 5 Logs detailed information that is useful for debugging the driver. 6 Logs all driver activity. Does it take a long time for the dashboards to refresh in Tableau? You may also want to look at the query profiles in Drill as well. --Andries On 11/6/17, 5:16 PM, "Divya Gehlot" <[email protected]> wrote: Hi Andries, Thanks for the advise . I am using Drill 1.10 and Tableau version 10.4 . I am connecting Drill thorugh Apache Drill connector. By Posting in community I wanted the know whether the issue is at tableau server or at Apache Drill ? Thanks, Divya On 3 November 2017 at 22:05, Andries Engelbrecht <[email protected]> wrote: > Use Drill 1.10 with the current published ODBC driver, there may be some > issues with Drill 1.11. > Also use Tableau 10.2+ with the Apache Drill connector. This works much > better than generic ODBC. > Make sure you can connect to Drill via ODBC, use Drill Explorer as example. > > Also look at some Drill Best Practices for BI Tools > https://community.mapr.com/community/exchange/blog/2017/ > 01/25/drill-best-practices-for-bi-and-analytical-tools > > > —Andries > > > > > On Nov 3, 2017, at 12:57 AM, Divya Gehlot <[email protected]<mailto: > [email protected]>> wrote: > > Hi, > I am getting protocol disconnected error in tableau. > When checked the drill logs I could see below > > 2017-11-03 07:51:52,798 [BitServer-4] WARN > o.a.drill.exec.work.foreman.Foreman - Dropping request to move to > COMPLETED > state as query is already at CANCELED state (which is terminal). > 2017-11-03 07:51:52,798 [BitServer-4] WARN > o.a.d.e.w.b.ControlMessageHandler - Dropping request to cancel fragment. > 2603e022-e3c1-e5a7-d54f-08e1399b4936:0:0 does not exist. > 2017-11-03 07:51:52,805 [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] > > > As suggested by one of the Drill user I set the > rpc: { > user: { > timeout: 30 > } > }, > > When I set above conf then could see the the dashboard is still in loading > state while no error log in drill. > > Appreciate the help to resolve the issue! > > Thanks, > Divya >
