[
https://issues.apache.org/jira/browse/AMBARI-21497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112451#comment-16112451
]
Hadoop QA commented on AMBARI-21497:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12880197/AMBARI-21497.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11922//console
This message is automatically generated.
> Conflicts in the ambari config groups
> -------------------------------------
>
> Key: AMBARI-21497
> URL: https://issues.apache.org/jira/browse/AMBARI-21497
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.1
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21497_branch-2.5.patch, AMBARI-21497.patch
>
>
> Ambari is arbitrarily changing settings for different config groups when
> pushing changes to other config groups.
> This is causing yarn to have settings for RAM that well exceed system limits,
> which causes other processes to run out of RAM and then become unavailable.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
