Community Articles
Find and share helpful community-sourced technical articles
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.
Cloudera Employee

If you see errors related to YARN Registry DNS Bind Port.

93400-yarn-registry-dns-port-conflict.png

Where the YARN Registry DNS is stopped, most probably due to a port conflict. Then go into the Advanced Configurations.

93402-yarnconfig.png

Look for the parameter RegistryDNS Bind Port and change is to a port that does not have a conflict. I changed it from 53 to 553.

Save configuration changes. Restart all components that are impacted.

93403-registrydnsbindport.png

This should take care of the issue and YARN Registry DNS will start successfully.

93404-yarnissueresolved.png


yarn-registry-dns-port-conflict.png
1,802 Views
Don't have an account?
Coming from Hortonworks? Activate your account here
Version history
Revision #:
2 of 2
Last update:
‎08-17-2019 06:00 AM
Updated by:
 
Contributors
Top Kudoed Authors