I've got a problem with my resourcemanager in yarn-site.cml config after enabling RM high availability. First I had a resource manager at Server1, then when I installed Server2, and enabled RM HA, Server2 became the "active" resourcemanager. My problem is that Ambari leaves the "old" configs of "yarn.resourcemanager.scheduler.address" set to "Server1" when adding the "yarn.resourcemanager.cluster-id" and other "yarn.resourcemanager.hostname.rm1" ..rm2 etc entries under the Custom yarn-site field in Ambari to contain both Server1 and Server2. When I try to run my yarn apps they try to connect to Server1 port 8030, which it's not listening on, since it is "Standby Resourcemanager". I'd expect it to connect to the "yarn-cluster" name as defined in "yarn.resourcemanager.cluster-id", not specific hostname of the old Resource manager. Is there something i'm overlooking in ambari configs, or is this a (known) bug? ... View more