Support Questions

anshul_sisodia · ‎06-14-2016

Hortonworks documentation says 8050 but yarn-default.xml says 8032. Also when I do netstat on resource manager node, it give 8032 port where resource manager is connecting and not 8050. I have got reference from one of the questions asked in community and it says this is a bug but might be a documentation error and docment team from Hortonworks has confirmed the port is 8032. See the below link and the update provided by Artem Ervits in the end:

https://community.hortonworks.com/questions/11599/how-to-change-resourcemanager-port-on-oozie.html#a...

Could anyone confirm and let me know if its being resolved?

@Artem Ervits @Neeraj Sabharwal @pardeep

KuldeepK · ‎06-15-2016

@Anshul Sisodia

In YARN HA, the property "yarn.resourcemanager.address" is redundant and instead "yarn.resourcemanager.address.X" is the one which is used.

.

1.) Ambari UI for YARN, shows only the property - yarn.resourcemanager.address And it uses port 8050 by default.

.

2.) In YARN UI, for the yarn configuration, the property is : yarn.resourcemanager.address.X yarn.resourcemanager.address.Y and they are using port 8032 by default.

.

Ambari UI does not explicitly shows "yarn.resourcemanager.address.X" or "yarn.resourcemanager.address.Y", rather only shows "yarn.resourcemanager.address".

.

In case if the requirement is to use a different port for the YARN HA ( other than 8032 ), then we can add "yarn.resourcemanager.address.X" and "yarn.resourcemanager.address.Y" in Ambari UI for customer yarn configuration.

.

Hope this information helps!

Happy Hadooping 🙂

View solution in original post

anshul_sisodia · ‎07-05-2016

Is it a bug that shows port 8050 in Ambari UI but connect to port 8032..?? I still dont understand as why it doesn't connect to 8050 if we have set Yarn.resourcemanager.address to <rmaddress:8050> rather than connecting to 8032.

rpathak · ‎07-05-2016

@Anshul Sisodia

As Kuldeep pointed out when you have your RM in HA mode, yarn.resourcemanager.address value is not used to bind the port.

Instead it uses port specified in yarn.resourcemanager.address.{rm1,rm2} for respective RMs.

By default the value is 8032. Also Ambari do not set this by default.

jimmyaneja · ‎03-31-2017

Hi in my case, I am seeing connection refused errors and in the url I notice that It says yarn.resourcemanager.address.X/ipaddress:port, my question is why do we have url/Ip_address:port instead of url:port?

jimmyaneja · ‎03-31-2017

2017-03-30 18:17:25,834 [JobControl] WARN org.apache.hadoop.ipc.Client - Failed to connect to server: blah-1-001.blah.blah.blah.blah-blah.com/50.0.0.11:8032: retries get failed due to exceeded maximum allowed retries number: 0 java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)

mukund_agilisiu · ‎08-18-2017

Hi,

When submitting a job via Oozie, I am also getting a Connection Refused error, after configuring yarn.resourcemanager.address.X & yarn.resourcemanager.address.Y and using port 8032.

I have RM HA and Name Node HA

For some reason, it is attempting to connect to the standby RM and not the Active RM

Cloudera Community

Support Questions

What is the default Yarn resource manager port. Is it 8032 or 8050 in HDP2.3.4 and above.