HiveServer not starting on docker image of apache ambari. Getting Couldn't resolve host error.

[#1]

Hi,

While starting Hiveserver2 in apache ambari, I'm getting "Couldn't resolve host" issue.

My ambari setup is a docker image having 3 clusters.

I can see that, as part to resolve the host it is taking the docker container name followed by the port no. I completely doubt if that is going to work.

http://16aadcc9c315:50070 not sure why it is like this.

16aadcc9c315 is the name of one of my cluster which is a docker image.

Any input on this will be appreciable?

Below is the error in logs file:

[#2]

My Bad, I cloned it from github. Below is the link.

https://github.com/weiqingy/caochong

[#3]

@Amit Kumar

Not sure if there is anything special in the above mentioned docker instance.

However if you would like to see Ambari's Docker instance / instructions then you might want to look at:

https://cwiki.apache.org/confluence/display/AMBARI/Development+in+Docker

https://github.com/apache/ambari/tree/trunk/dev-support/docker

And

https://github.com/sequenceiq/docker-ambari The above Github repo has more contributors and more Commits. This worked for me many times.

[#4]

So no way to resolve this issue of unknown host name?

[#5]

@Amit Kumar It will be more of troubleshooting docker based n/w config. We may need to look from the docker side much... compared to ambari/hive side.

[#6]

Agreed! I'll check for the images provided by you. All thanks!

[#7 · Accepted solution]

@Jay SenSharma

I was able to fix this by adding the hostname and ip of every cluster in /etc/hosts. I was able to ping after that with the hostname. This worked for me.

All thanks for the input.

[#8]

@Amit Kumar

How did you add the entries in the "/etc/hosts" file something like below ... or in a different way ? AS we already discussed about it .... and i though it did not work for you?

172.20.0.2   8c043e0d490c
172.20.0.3   16aadcc9c315
172.20.0.4   b1ec39e6d58b

[#9]

Yes, it is the same way you mentioned.

I think, I misinterpreted you response and responded wrongly. For each cluster, there were only one entry. I added rest of the two.