NodeManager shuts down if it can't find the ResourceManager

When starting yarn services, and if the NodeManager is started but the ResourceManager is not. The NodeManager tries 10 times (the default setting), and then shuts down.

I understand that this default setting can be changed and possibly wait for a longer period, but I think it is better to keep the NodeManager trying without shutting down. This can accomodate cases where the ResourceManager is late to start for any problems and it will preserve the same behavior to what the DataNode does when it cannot find the NameNode at startup as it keeps trying without shutting down.