You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Nate Cole (JIRA)" <ji...@apache.org> on 2013/11/07 14:23:24 UTC

[jira] [Commented] (AMBARI-3672) Add Support to AmbariManagementController to derive configs from Config groups

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

Nate Cole commented on AMBARI-3672:
-----------------------------------

Patch is looking good.  One question though.  Let's pretend you have a cluster, that has some config groups defined.  But then, you have just one host, already part of a config group where you want to tweak, say, some heap settings.  Do you create a completely new ConfigGroup for that one host, or do/can you override that one host directly?

> Add Support to AmbariManagementController to derive configs from Config groups
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-3672
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3672
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>    Affects Versions: 1.4.2
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.4.3
>
>         Attachments: AMBARI-3672.patch
>
>
> Application of the configurations boils down to figuring out the configs for a Service Host Component when a Task is to be created for the host. Rules to apply configuration changes:
> - Apply cluster desired configs
> - Get all the config groups for the host
> - Apply the overrides per config type.  (In future this can go through config groups for service then component and host component in that order)



--
This message was sent by Atlassian JIRA
(v6.1#6144)