[
https://issues.apache.org/jira/browse/AMBARI-21497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16112513#comment-16112513
]
Hudson commented on AMBARI-21497:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7838 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7838/])
AMBARI-21497 Conflicts in the ambari config groups. (atkach) (atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b17225df413ee0f6e562769963df864c69a02821])
* (edit) ambari-web/app/mixins/common/configs/configs_saver.js
* (edit) ambari-web/app/mixins/common/configs/enhanced_configs.js
* (edit) ambari-web/test/mixins/common/configs/enhanced_configs_test.js
* (edit) ambari-web/test/mixins/common/configs/configs_saver_test.js
> 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)
