https://community.cloudera.com/t5/Support-Questions/INFO-yarn-ApplicationMaster-Unregistering-ApplicationMaster/m-p/230856#M192703 <P><A rel="user" href="https://community.cloudera.com/users/46170/hadoopammireddy.html" nodeid="46170">@deepak rathod</A></P><P>Is this happening with all the jobs? For example even with some long running jobs?</P><P>Sometimes it can happen when the Spark job finishes fine but too early, But the executors are still trying to contact driver, Hence ultimately yarn declares the job as failed since executors could not connect.</P><P>.</P><P>It can also happen if there is a Firewall (Network issue) if some ports are blocked. So you might want to check if the ports are accessible properly or not? Mostly the port are chosen at random in spark, but you may try setting spark.driver.port to see if it is accessible remotely and helps. For other ports please refer to: </P><P><BR /><A href="http://spark.apache.org/docs/latest/security.html#configuring-ports-for-network-security" target="_blank">http://spark.apache.org/docs/latest/security.html#configuring-ports-for-network-security</A></P><P><A href="http://spark.apache.org/docs/latest/configuration.html#networking" target="_blank">http://spark.apache.org/docs/latest/configuration.html#networking</A> </P><P>.</P> Fri, 20 Oct 2017 14:04:05 GMT jsensharma 2017-10-20T14:04:05Z