ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-17835) Maximum validation failure for 'yarn.scheduler.maximum-allocation-mb' after dependency change
Date Fri, 22 Jul 2016 12:16:20 GMT

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

Dmytro Sen commented on AMBARI-17835:
-------------------------------------

Failed unit tests aren't related to this jira

> 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-trunk.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