Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here. Want to know more about what has changed? Check out the Community News blog.

Bad health node not decommisoned then what will happen

Bad health node not decommisoned then what will happen

New Contributor

Hi All,

 

We had a bad health node on our cluster, we have requested server team to look into that particular server. Apparently if we didn't decommission the bad health node if so what would impact.users will get any errors ?

we hope if server rebooted then node automatically will pick this node up, hence we can avoid decommission and recommission of the node, even restart not required.

 

Please let us know if my undertandings are wrong. Thanks

 

Regards,

Naga.S

2 REPLIES 2

Re: Bad health node not decommisoned then what will happen

Champion
Is the bad health HDFS or YARN related or another services? Most issues can be fixed without needing to decomm/recomm. So yes if you don't decomm it then it will stay in place and other services can still use it. For example, if The DN is offline, YARN containers can still run on it they will just stream data over from other DNs. That is generally the impact. Both YARN and HDFS have mechanisms to black list a node if it is having issues. So some jobs may encounter failures and for a YARN job if that is four failures for a singe job then it will fail. But most one hit that situation, they will recover and continue on. So most users won't even notice.

Re: Bad health node not decommisoned then what will happen

New Contributor

Thanks for the clear explanation.