Yarn-site template for SSL

[#1]

Hi,

I have all YARN WebUI's running on SSL. This results in the nodemanagers webUI running on port 8044 instead of the default, which is 8042. The NM WebUI is available at 8044.

Now I see lots of Ambari alerts, since Ambari still calls port 8042 for performing YARN health checks.

There are 2 options here:

1.)

Make NM start its webUI on 8042 still (with SSL). The default yarn-site.xml has this

yarn.nodemanager.webapp.address

${yarn.nodemanager.hostname}:8042

but apparently this is changed into 8044 (maybe in Yarn source code, maybe by Ambari yarn config templates (??)

or

2.)

Notify Ambari somehow to do the YARN health check on the correct port; 8044

So, far I could make neither work for me. Please help

[#2]

Hi @Jasper

I believe your alert.json would be still pointing to 8042. Could you please try below steps?

1. Go to your Ambari server.
2. vi /var/lib/ambari-server/resources/common-services/YARN/2.1.0.2.0/alerts.json
Please change "2.1.0.2.0" according to your environment.
3. Change "default_port" from 8042 to 8044.
4. Save the file and restart Ambari server.

[#3]

@Vaisakh Sundaram

I tried your approach, but after the server restart it does not stop the alert to still call on port 8042 instead of 8044.

[#4 · Accepted solution]

I have a solution for option 1.) now.

If you add a custom yarn-site.xml property on Ambari like below, the SSL nodemanager WebUI starts on port 8042

yarn.nodemanager.webapp.https.address 0.0.0.0:8042