You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Oleg Nechiporenko (JIRA)" <ji...@apache.org> on 2015/04/03 12:25:52 UTC

[jira] [Commented] (AMBARI-10342) Dependent config changes not being shown to user

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

Oleg Nechiporenko commented on AMBARI-10342:
--------------------------------------------

+1 for patch

> Dependent config changes not being shown to user
> ------------------------------------------------
>
>                 Key: AMBARI-10342
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10342
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10342.patch
>
>
> According to the configs document, when the config yarn.scheduler.minimum-allocation-mb is updated, a bunch of other configs should be updated after call to /recommendations.
> From the UI when I make a change to yarn.scheduler.minimum-allocation-mb, I see the correct API call made. I also see one of the configs mapreduce.map.memory.mb's value change from 682 => 1024. However, there is no message saying 'X configs in Y services changed' etc.
> We should make sure that the response's values, min, max, step, etc. should be updated live in the configs.



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