[
https://issues.apache.org/jira/browse/AMBARI-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-2298:
-----------------------------------
Labels: pull-request-available (was: )
> YARN/MR2 do not start after reconfiguring
> -----------------------------------------
>
> Key: AMBARI-2298
> URL: https://issues.apache.org/jira/browse/AMBARI-2298
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.4.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.4.0
>
> Attachments: AMBARI-2298_branch-1.4.0.patch
>
>
> After successfully installing a cluster, I saved YARN configs (changed only 1
> property). YARN service would not start with ResourceManager saying it cannot
> bind to port.
> Turns out that certain properties in {{yarn-site.xml}} were set to null value.
> {noformat}
> "yarn.resourcemanager.admin.address" : "null",
> "yarn.resourcemanager.resource-tracker.address" : "null",
> "yarn.resourcemanager.scheduler.address" : "null",
> "yarn.resourcemanager.address" : "null",
> "yarn.log.server.url" : "null",
> {noformat}
> Similar problem with MR2 also. The {{mapred-site.xml}} had 19 properties
> which were null.
> {noformat}
> "mapred.jobtracker.taskScheduler" : "null",
> "mapred.tasktracker.map.tasks.maximum" : "null",
> "mapred.hosts.exclude" : "null",
> ....
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
