You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Akhil S Naik (JIRA)" <ji...@apache.org> on 2018/08/07 07:03:00 UTC

[jira] [Commented] (AMBARI-24370) Config Group - unable to remove config setting

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

Akhil S Naik commented on AMBARI-24370:
---------------------------------------

Hi [~harisekhon],

As per latest Ambari and corresponding Docs. , The Ambari never support a feature of Removing the config group.

https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/managing-and-monitoring-ambari/content/amb_edit_setting_for_a_configuraton_group.html

you can only override the configurations.

if you would like to achieve the same.
 delete it from default config and add it to a separate config group where it contains the required nodes which need the config.

you might need to keep two config groups then.




> Config Group - unable to remove config setting
> ----------------------------------------------
>
>                 Key: AMBARI-24370
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24370
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 2.5.2
>            Reporter: Hari Sekhon
>            Priority: Major
>
> Config Group overrides are unable to remove a setting from being set at all in existing default config.
> For example, setting bucket cache on HBase default config group will break HMasters so if you put the HMasters in a separate config group you are unable to remove the settings (setting to zero or none still breaks HMasters, you need to completely unset the config from existing).
> Instead you have to move all the RegionServers to another config group, leave the default config group without the setting and then set the config only as an override such that it doesn't exist in default group that HMasters use.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)