ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Sposetti (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-10434) Reverting config (by clicking default) does not revert changed configs warnings
Date Thu, 16 Apr 2015 16:39:59 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeff Sposetti updated AMBARI-10434:
-----------------------------------
    Fix Version/s: 2.1.0

> 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
>            Assignee: Andrii Babiichuk
>             Fix For: 2.1.0
>
>         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)

Mime
View raw message