[
https://issues.apache.org/jira/browse/AMBARI-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13824347#comment-13824347
]
Yusaku Sako edited comment on AMBARI-3783 at 11/16/13 9:20 PM:
---------------------------------------------------------------
[~srimanth.gunturi], "config_groups.update" uses the *async: false* option.
We should move away from using this option in general as it prevents
parallelism and blocks the UI, etc., leading to unresponsive UI, especially
when multiple calls are being made.
We can create another ticket and optimize later, but my opinion is that any new
code we write, we should not be using this option.
was (Author: u39kun):
[~srimanth.gunturi], "config_groups.update" uses the *async: false* option.
Let's not do that.
> Hitting Save in the config-group does not update host membership
> ----------------------------------------------------------------
>
> Key: AMBARI-3783
> URL: https://issues.apache.org/jira/browse/AMBARI-3783
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.4.2
> Reporter: Srimanth Gunturi
> Assignee: Srimanth Gunturi
> Fix For: 1.4.2
>
> Attachments: AMBARI-3783.patch
>
>
> In the {{Manage HDFS Configuration Groups}} dialog, I was able to select
> hosts for a config-group. However when I hit Save, the changes were not
> persisted.
> Also, the Save button should be enabled only when host memberships have been
> changed.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
