What is the error for the collocated Drillbit instance ? Did you apply the 
"DRILL_HOST_NAME" to the collocated Drillbit's drill-env.sh file as well?

One quick test is to try if the ZK port is accessible locally, but not using 
the loopback IP (i.e. 127.0.0.1 ). Telnet is a good way to verify that you're 
able to connect. 

 

-----Original Message-----
From: Knapp, Michael [mailto:michael.kn...@capitalone.com] 
Sent: Friday, March 31, 2017 11:41 AM
To: user@drill.apache.org
Subject: Struggling to run in distributed mode

Hi,

I am struggling to get drill to run in distributed mode.  I stood up two Amazon 
EC2 instances using amazon’s linux for the OS, on m4.large instances.  I 
decided to install zookeeper on one of them.  I also have java 8 installed on 
each of them.  I followed the instructions provided here:
https://drill.apache.org/docs/installing-drill-on-the-cluster/

My drill-override.conf file is the same on each node, it looks like this:

drill.exec: {
  cluster-id: "drillbits1",
  zk.connect: "10.XXX.YYY.ZZZ:2181"
}

The IP address of the zookeeper is the same as one of the drill nodes, because 
it is running on the same machine.  Unfortunately for me, drillbit.sh fails.

On the machine that is co-located with zookeeper, I get this IOException in the 
drillbit.out file:
Failure to connect to the zookeeper cluster service within the allotted time of 
10000 milliseconds I have confirmed that ZK is running and I can open a shell 
to it.

On the machine that is NOT co-located with zookeeper, I get a 
DrillbitStartupException: Drillbit is disallowed to bind to loopback address in 
distributed mode.  I looked in the drillbit.log file, it has:
host.name=ip-10-XXX-YYY-ZZZ.****.com.

After reviewing the source code, I realized that Drill lets you override the 
host name from drill-env.sh.  By setting “DRILL_HOST_NAME” to the IP address, I 
was able to start the Drill instance that is NOT co-located with Zookeeper.  
However, the same solution did not work with the instance that is co-located 
with zookeeper, it is still failing with a timeout while trying to connect with 
Zookeeper.

I do not understand why this is not working, would somebody please explain what 
is happening?
Also, would somebody please update the installation instructions to explain 
when I need to set the “DRILL_HOST_NAME”?
Last and most importantly, why is my Drill instance unable to connect with 
Zookeeper on its own machine?

Michael Knapp



________________________________________________________

The information contained in this e-mail is confidential and/or proprietary to 
Capital One and/or its affiliates and may only be used solely in performance of 
work or services for Capital One. The information transmitted herewith is 
intended only for use by the individual or entity to which it is addressed. If 
the reader of this message is not the intended recipient, you are hereby 
notified that any review, retransmission, dissemination, distribution, copying 
or other use of, or taking of any action in reliance upon this information is 
strictly prohibited. If you have received this communication in error, please 
contact the sender and delete the material from your computer.

Reply via email to