ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14679) When Spark is added later to a cluster with YARN deployed then yarn-site is not modified
Date Sat, 16 Jan 2016 06:13:39 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-14679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103020#comment-15103020
] 

Hadoop QA commented on AMBARI-14679:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12782628/AMBARI-14679.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/4954//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/4954//console

This message is automatically generated.

> 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
>
>         Attachments: AMBARI-14679.patch
>
>
> 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 :
> {code}
>  'yarn.nodemanager.aux-services': 'mapreduce_shuffle,spark_shuffle'
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message