You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/02/15 12:23:00 UTC
[jira] [Commented] (AMBARI-2298) YARN/MR2 do not start after
reconfiguring
[ https://issues.apache.org/jira/browse/AMBARI-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365462#comment-16365462 ]
Hudson commented on AMBARI-2298:
--------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8735 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8735/])
AMBARI-2298. Not able to add Livy2 after doing rolling upgrade to M21 (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=4af9d720967bb90842bc91533b22611ba21bacdb])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog262.java
AMBARI-22986. Not able to add Livy2 after doing rolling upgrade to M21 - (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=fa7c3952d7464c7dbd778baa2b8ea2f4470d2f3d])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog262.java
AMBARI-22986. Not able to add Livy2 after doing rolling upgrade to M21 - (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=bbb590026b788eaefc63962277621fa487a4e615])
* (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UpgradeResourceProviderTest.java
> 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
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 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)