Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 373FF18378 for ; Wed, 2 Dec 2015 17:45:11 +0000 (UTC) Received: (qmail 97442 invoked by uid 500); 2 Dec 2015 17:45:11 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 97409 invoked by uid 500); 2 Dec 2015 17:45:11 -0000 Mailing-List: contact dev-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 dev@ambari.apache.org Received: (qmail 97394 invoked by uid 99); 2 Dec 2015 17:45:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Dec 2015 17:45:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E529C2C0453 for ; Wed, 2 Dec 2015 17:45:10 +0000 (UTC) Date: Wed, 2 Dec 2015 17:45:10 +0000 (UTC) From: "Aravindan Vijayan (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-14120) AMS Collector and HBase heap memory config properties are incompatible between 2.1.2 and 2.1.3 when deployed through the same blueprint. 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-14120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-14120. ---------------------------------------- Resolution: Fixed > AMS Collector and HBase heap memory config properties are incompatible between 2.1.2 and 2.1.3 when deployed through the same blueprint. > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: AMBARI-14120 > URL: https://issues.apache.org/jira/browse/AMBARI-14120 > Project: Ambari > Issue Type: Bug > Affects Versions: 2.1.3 > Reporter: Aravindan Vijayan > Assignee: Aravindan Vijayan > Priority: Critical > Fix For: 2.1.3 > > Attachments: AMBARI-14120.patch > > > PROBLEM > On Version 2.1.2, AMS had no "m" in the heap properties in the *-env.sh templates and the user was expected to specify the "m" suffix through the UI config. > On Version 2.1.3, AMS had the "m" suffix in the heapsize properties in the *-env.sh templates, and the user was not allowed to give the "m" suffix in the UI. > When a 2.1.2 blueprint is used to deploy Ambari 2.1.3, AMS does not start due to invalid heap properties. > FIX > The input heapsize parameter can either be 512 (UI) or 512m (blueprint). The "m" is added to the former case programmatically to achieve uniformity. The ams-hbase-content will not have "m" appended to any property. -- This message was sent by Atlassian JIRA (v6.3.4#6332)