Yarn: how to specify the hostname/IP for communication between the ResourceManager and the NodeManager for a Kubernetes deployment.

Hello, Tl;dr question: How to make the NodeManager give the "yarn.nodemanager.hostname" value to the Yarn ResourceManager during registration for IPC communication. Explanations: I have trouble making a Yarn cluster works in a Kubernetes deployment where every components run as a Docker

Re: failed to start namenode

Are you sure the host is up? On Friday, 20 November 2015, siva kumar wrote: > Hi Sandeep, > Im tryning to start using cloudera manager . This > is the error message im getting. The log is not getting generated in the > log directory. > > Supervisor

Re: failed to start namenode

Hi Sandeep, Im tryning to start using cloudera manager . This is the error message im getting. The log is not getting generated in the log directory. Supervisor returned FATAL. Please check the role log file, stderr, or stdout. HTTP ERROR 502 Problem accessing

Re: Yarn application reading from Data node using short-circuit.

Thanks Chris, I went through the description on the link and found out that I had not added YARN user in list of allowed users to read from unix sockets. I've added it now and re running the load to see if there is any improvement. Regards, Sandeep On Thu, Nov 19, 2015 at 10:52 PM, Chris

Re: Yarn: how to specify the hostname/IP for communication between the ResourceManager and the NodeManager for a Kubernetes deployment.

Hi I think you should try the Service IP and DNS solution. The Service IP is a virtual IP and also a rule in iptables, it's life cycle is managed by end-users, thus it is suitable being recorded in DNS. So back to this case, you could create the Service layer first. And since its FQDN is