Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Community Articles

Find and share helpful community-sourced technical articles.
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!
avatar
Contributor

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
4,129 Views
Version history
Last update:
‎08-17-2019 06:00 AM
Updated by:
Contributors