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 90ECF18A3A for ; Sun, 21 Jun 2015 21:57:00 +0000 (UTC) Received: (qmail 96900 invoked by uid 500); 21 Jun 2015 21:57:00 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 96866 invoked by uid 500); 21 Jun 2015 21:57: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 96853 invoked by uid 99); 21 Jun 2015 21:57:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Jun 2015 21:57:00 +0000 Date: Sun, 21 Jun 2015 21:57:00 +0000 (UTC) From: "Antonenko Alexander (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-12059) YARN tab should be before MapReduce2 tab when setting up configs in the launch wizard 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-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-12059: ----------------------------------------- Committed to trunk > YARN tab should be before MapReduce2 tab when setting up configs in the launch wizard > ------------------------------------------------------------------------------------- > > Key: AMBARI-12059 > URL: https://issues.apache.org/jira/browse/AMBARI-12059 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 2.1.0 > Reporter: Antonenko Alexander > Assignee: Antonenko Alexander > Fix For: 2.2.0 > > Attachments: AMBARI-12059.patch > > > MR configs rely on YARN configs for certain sizing i.e. map memory and reduce memory is dependent on yarn minimum allocation. > When trying to size MR configs, the minimum limit starts 0.66 GB on a 2 node vagrant cluster. There is no clear indication to the user why this min limit is setup. Allow the user to progress to YARN first before tweaking MR configs would be better. -- This message was sent by Atlassian JIRA (v6.3.4#6332)