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 2860917E38 for ; Mon, 22 Jun 2015 11:29:01 +0000 (UTC) Received: (qmail 87983 invoked by uid 500); 22 Jun 2015 11:29:00 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 87919 invoked by uid 500); 22 Jun 2015 11:29:00 -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 87544 invoked by uid 99); 22 Jun 2015 11:29:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jun 2015 11:29:00 +0000 Date: Mon, 22 Jun 2015 11:29:00 +0000 (UTC) From: "Andrii Babiichuk (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-12016) Going over maximum in config-group shows errors in default-config-group 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-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk resolved AMBARI-12016. --------------------------------------- Resolution: Fixed > Going over maximum in config-group shows errors in default-config-group > ----------------------------------------------------------------------- > > Key: AMBARI-12016 > URL: https://issues.apache.org/jira/browse/AMBARI-12016 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 2.1.0 > Reporter: Andrii Babiichuk > Assignee: Andrii Babiichuk > Priority: Critical > Fix For: 2.1.0 > > > # Installed a brand new cluster > # Went to YARN service and created a new config-group with 1 host. > # Selected the config-group and overrode {{yarn.nodemanager.resource.memory-mb}} and moved the value from 2048 to 2304. > # Because of above step {{yarn.scheduler.maximum-allocation-mb}} also moved to 2304, but was shown as an error (even when API bumped up maximum to 2304). *Problem 1* > # Saved the config-group - hit a blank page. > # Went back to default-config-group. > # Reloaded page > # *Problem 2* - The overridden value for new config-group is still shown as 2048 when it should have been 2304. -- This message was sent by Atlassian JIRA (v6.3.4#6332)