You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Mrudula Madiraju (JIRA)" <ji...@apache.org> on 2017/10/13 14:48:00 UTC

[jira] [Comment Edited] (AMBARI-9255) Show why Configs Save button is disabled

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

Mrudula Madiraju edited comment on AMBARI-9255 at 10/13/17 2:47 PM:
--------------------------------------------------------------------

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

yarn.resourcemanager.zk-address 
and
hadoop.registry.zk.quorum




was (Author: mrudulam):
The same issue occurs for Yarn if the following parameters are not filled. Again they do not show up unless explicitly specified.

yarn.resourcemanager.zk-address 
and
hadoop.registry.zk.quorum

!attachment-name.jpg|thumbnail!

> Show why Configs Save button is disabled
> ----------------------------------------
>
>                 Key: AMBARI-9255
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9255
>             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
(v6.4.14#64029)