05-14-2018 01:07 PM
We have a pretty old CDH 5.7 cluster that works fine. But when we try to add a second Resource manager and enable high availability, both RM's remain in standby state and there is no active one.
This seems to be a known issue and the suggested fix is to run "yarn resourcemanager -format-state-store". Cloudera itself recoomends it here (search for "standby") and so does other articles on the web. However, running this and restarting the RM's did not solve our problem.
I also couldn't find anything special in the logs, and to make things even more strange, we have another 5.7 cluster where we successfuly enabled YARN high availability without issues.
Does anyone have an idea what's wrong ? Did anyone have such issue ?
05-14-2018 06:43 PM
06-27-2018 07:25 AM
I think the sulotion is to format the RMStateStore :
yarn resourcemanager -format-state-store
10-07-2018 10:01 PM
While doing the manual failover in resource manager my schduled and running application id's will it move to stanby resource manager buy how? In hdfs name node journal nodes are monitoring the edit logs. In resource manager which daemon is monitoring?