Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

YARN NODEMANAGER BIND TO INTERNAL IP

Highlighted

YARN NODEMANAGER BIND TO INTERNAL IP

Rising Star

I am facing security harden request due to nodemanager expose the internal IP when I run below command

printf "GET / HTTP/1.0\n\nHost:152.220.128.107:8042\n\nUser-Agent:Feedburner\n\n" | nc 152.220.128.107 8042

and result is

Connection to 152.220.128.107 8042 port [tcp/fs-agent] succeeded!

HTTP/1.1 302 Found

Cache-Control: no-cache

Expires: Tue, 20 Sep 2016 16:04:02 GMT

Date: Tue, 20 Sep 2016 16:04:02 GMT

Pragma: no-cache Expires: Tue, 20 Sep 2016 16:04:02 GMT

Date: Tue, 20 Sep 2016 16:04:02 GMT

Pragma: no-cache Content-Type: text/plain; charset=UTF-8

Location: http://10.50.12.217:8042/node

Content-Length: 0 Server: Jetty(6.1.26.hwx)

from above result it shows 10.50.12.217 which is the host private IP. meanwhile, I am using AWS EC2 which the server interface bind only for internal IP.

So my questions is . Is there any way I can get this internal gone? or make it as server FQDN.

I've checked some documents which said I have to set

yarn.nodemanager.hostname as FQDN?

Thanks in advance.

Don't have an account?
Coming from Hortonworks? Activate your account here