From issues-return-66773-archive-asf-public=cust-asf.ponee.io@ambari.apache.org Thu Feb 15 13:23:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id E8B3B18067B for ; Thu, 15 Feb 2018 13:23:04 +0100 (CET) Received: (qmail 31414 invoked by uid 500); 15 Feb 2018 12:23:04 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 31405 invoked by uid 99); 15 Feb 2018 12:23:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Feb 2018 12:23:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7012A180025 for ; Thu, 15 Feb 2018 12:23:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id xKl7vZ1W-yGn for ; Thu, 15 Feb 2018 12:23:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 2D3395F18F for ; Thu, 15 Feb 2018 12:23:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5C2E8E0231 for ; Thu, 15 Feb 2018 12:23:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 313FA21E5E for ; Thu, 15 Feb 2018 12:23:00 +0000 (UTC) Date: Thu, 15 Feb 2018 12:23:00 +0000 (UTC) From: "Hudson (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-2298) YARN/MR2 do not start after reconfiguring MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)