What ZK are you using , Apache? Also the can the client system resolve the hostname of the VM with Drill on it?
In simplified terms the connection will work like this. Client connects to ZK (port 2181 or 5181 pending which ZK is used), ZK returns the hostname of the VM (not IP) and also which drillbit to connect to. Client connects to drillbit on port 31010. Make sure ZK ports and drill ports are open, and also hostname resolution is in place (/etc/hosts for Linux/Mac, or /windows/system32/driver/etc/hosts for windows typically). Also with VMs you need to check if you use NAT or bridged adapter, I prefer bridged adapter to get a separate IP from the host system. --Andries > On Jan 13, 2016, at 4:48 PM, Timothy Findlay <timothyfind...@nbnco.com.au> > wrote: > > Hi, > > I know this sounds crazy, but here is how I got the problem. > > - I downloaded Drill 1.4.0 and dropped it in a Centos VM (Virtualbox) > > - Configured Zookeep, Started Drill service (daemon) > > - Tested using SQLLine, all good. > > - Picked the drill-jdbc-all-1.4.0.jar from the JAR's folder > > - Started Squirrel as described. Added the driver, with the JAR, set > the Driver name > > - Created an Alias and set the URL to jdbc:drill:zk=192.168.56.102:2181 > > - Trying to connect I get Caused by: > oadd.org.apache.drill.exec.rpc.RpcException: CONNECTION : > java.net.ConnectException: Connection refused: no further information: > localhost/127.0.0.1:31010 > > I've checked the VM, there's no firewall or anything stopping it. But if you > look closely, where the heck is it getting port 31010 from ? and Drill is > running on a VM, not localhost. > > What gives ? How can I put in configuration details and it seems to ignore > them. > > Any hints/tips would be appreciated. > > Tim.
