You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Babiichuk (JIRA)" <ji...@apache.org> on 2015/04/10 14:54:12 UTC
[jira] [Updated] (AMBARI-10434) Reverting config (by clicking
default) does not revert changed configs warnings
[ https://issues.apache.org/jira/browse/AMBARI-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrii Babiichuk updated AMBARI-10434:
--------------------------------------
Attachment: AMBARI-10434.patch
> Reverting config (by clicking default) does not revert changed configs warnings
> -------------------------------------------------------------------------------
>
> Key: AMBARI-10434
> URL: https://issues.apache.org/jira/browse/AMBARI-10434
> Project: Ambari
> Issue Type: Task
> Reporter: Andrii Babiichuk
> Attachments: AMBARI-10434.patch
>
>
> STR
> * Install cluster so that values are at the default values
> * Change {{yarn.scheduler.minimum-allocation-mb}} from default 682 to 1024.
> * The dependent configs correctly changed... their values derived from 1024.
> * Now I clicked on the default triangle to set value to 682.
> ** I see 2 POST calls... one for 683 value, and one for 682
> * I see {{yarn.scheduler.minimum-allocation-mb}} back to 682, but the service still says it has changed configs whose values are derived from 683.
> When we revert to original value, and dependent configs revert to original values, the warnings should go away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)