ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mrudula Madiraju (JIRA)" <>
Subject [jira] [Commented] (AMBARI-9255) Show why Configs Save button is disabled
Date Fri, 13 Oct 2017 11:24:00 GMT


Mrudula Madiraju commented on AMBARI-9255:

The same issue occurs for Yarn if the following parameters are not filled. Again they do not
show up unless explicitly specified.


> Show why Configs Save button is disabled
> ----------------------------------------
>                 Key: AMBARI-9255
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>    Affects Versions: 1.7.0
>            Reporter: Taeyun Kim
>            Priority: Minor
> After YARN Configs is changed and saved, there is a case that the saved configuration
itself bacomes invalid state(for example, some config value is missing).
> In my case, the missing one was 'yarn.resourcemanager.fs.state-store.uri'. But that variable
is hidden in the folded 'Advanced yarn-site' group, so there is no clue that some variable
has incorrect or missing value.
> So when I change an another config value, Discard button is enabled, but Save button
is not enabled. But I see no clue why.
> Here, there are 2 problems:
> 1. Incorrect state is saved by UI. It should not happen.
> 2. Sometimes it's hard to see what is wrong that's preventing Save.
> So, at least for the 2nd problem, it would be nice to show what is wrong.

This message was sent by Atlassian JIRA

View raw message