ambari-issues 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-17835) Maximum validation failure for 'yarn.scheduler.maximum-allocation-mb' after dependency change
Date Thu, 28 Jul 2016 07:09:20 GMT

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

Hadoop QA commented on AMBARI-17835:
------------------------------------

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

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8199//console

This message is automatically generated.

> Maximum validation failure for 'yarn.scheduler.maximum-allocation-mb' after dependency
change
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17835
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17835
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17835_2.patch
>
>
> STR
> 1) Set yarn.nodemanager.resource.memory-mb to be more than recommended default
> 2) click next



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

Mime
View raw message