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 BAD6F1831D for ; Fri, 15 Jan 2016 02:27:40 +0000 (UTC) Received: (qmail 22070 invoked by uid 500); 15 Jan 2016 02:27:40 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 22030 invoked by uid 500); 15 Jan 2016 02:27:40 -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 21843 invoked by uid 99); 15 Jan 2016 02:27:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jan 2016 02:27:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D8B522C1F5B for ; Fri, 15 Jan 2016 02:27:39 +0000 (UTC) Date: Fri, 15 Jan 2016 02:27:39 +0000 (UTC) From: "Swapan Shridhar (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-14679) When Spark is added later to a cluster with YARN deployed then yarn-site is not modified 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-14679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-14679: ------------------------------------- Description: If Spark is added to an existing cluster with YARN using HDP 2.4, then yarn-site:yarn.nodemanager.aux-services is not modified to include spark_shuffle. Recommendation show is : {code} Recommendations: {'yarn.timeline-service.entity-group-fs-store.group-id-plugin-classes': '', 'yarn.nodemanager.container-executor.class': 'org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor', 'yarn.nodemanager.aux-services.spark_shuffle.class': 'org.apache.spark.network.yarn.YarnShuffleService', 'yarn.scheduler.minimum-allocation-vcores': '1', 'yarn.scheduler.maximum-allocation-vcores': '1', 'yarn.nodemanager.resource.memory-mb': '1024', 'yarn.scheduler.minimum-allocation-mb': '341', 'yarn.nodemanager.resource.cpu-vcores': '1', 'yarn.nodemanager.aux-services': 'mapreduce_shuffle, 'yarn.scheduler.maximum-allocation-mb': '1024', 'yarn.nodemanager.linux-container-executor.group': 'hadoop'} {code} But with SPARK added, it should be : 'yarn.nodemanager.aux-services': 'mapreduce_shuffle,spark_shuffle' was: If Spark is added to an existing cluster with YARN using HDP 2.4, then yarn-site:yarn.nodemanager.aux-services is not modified to include spark_shuffle. It seems that recommendation provides it: {code} Recommendations: {'yarn.timeline-service.entity-group-fs-store.group-id-plugin-classes': '', 'yarn.nodemanager.container-executor.class': 'org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor', 'yarn.nodemanager.aux-services.spark_shuffle.class': 'org.apache.spark.network.yarn.YarnShuffleService', 'yarn.scheduler.minimum-allocation-vcores': '1', 'yarn.scheduler.maximum-allocation-vcores': '1', 'yarn.nodemanager.resource.memory-mb': '1024', 'yarn.scheduler.minimum-allocation-mb': '341', 'yarn.nodemanager.resource.cpu-vcores': '1', 'yarn.nodemanager.aux-services': 'mapreduce_shuffle, 'yarn.scheduler.maximum-allocation-mb': '1024', 'yarn.nodemanager.linux-container-executor.group': 'hadoop'} {code} With SPARK added, it should be : 'yarn.nodemanager.aux-services': 'mapreduce_shuffle,spark_shuffle' > When Spark is added later to a cluster with YARN deployed then yarn-site is not modified > ---------------------------------------------------------------------------------------- > > Key: AMBARI-14679 > URL: https://issues.apache.org/jira/browse/AMBARI-14679 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.2.1 > Reporter: Swapan Shridhar > Assignee: Swapan Shridhar > Priority: Critical > Fix For: 2.2.1 > > > If Spark is added to an existing cluster with YARN using HDP 2.4, then yarn-site:yarn.nodemanager.aux-services is not modified to include spark_shuffle. > Recommendation show is : > {code} > Recommendations: {'yarn.timeline-service.entity-group-fs-store.group-id-plugin-classes': '', 'yarn.nodemanager.container-executor.class': 'org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor', 'yarn.nodemanager.aux-services.spark_shuffle.class': 'org.apache.spark.network.yarn.YarnShuffleService', 'yarn.scheduler.minimum-allocation-vcores': '1', 'yarn.scheduler.maximum-allocation-vcores': '1', 'yarn.nodemanager.resource.memory-mb': '1024', 'yarn.scheduler.minimum-allocation-mb': '341', 'yarn.nodemanager.resource.cpu-vcores': '1', 'yarn.nodemanager.aux-services': 'mapreduce_shuffle, 'yarn.scheduler.maximum-allocation-mb': '1024', 'yarn.nodemanager.linux-container-executor.group': 'hadoop'} > {code} > But with SPARK added, it should be : > 'yarn.nodemanager.aux-services': 'mapreduce_shuffle,spark_shuffle' -- This message was sent by Atlassian JIRA (v6.3.4#6332)