You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2017/08/03 08:15:00 UTC
[jira] [Commented] (AMBARI-21497) Conflicts in the ambari config
groups
[ https://issues.apache.org/jira/browse/AMBARI-21497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112392#comment-16112392 ]
Andrii Tkach commented on AMBARI-21497:
---------------------------------------
branch-2.5:
30405 passing (25s)
157 pending
> 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
> Attachments: AMBARI-21497_branch-2.5.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)