Set up configuration groups

Object (cluster, service, component) general configuration is applicable to all hosts related to that object. The purpose of an object’s configuration group is to set a parameter for a particular host (or a group of hosts) that is different from the parameters of object’s general configuration.

Configuration (or config) group is created via ADCM interface. After config group is created, it is populated by hosts. Configuration parameters obtain checkboxes that provide an ability to configure a parameter at a host (or a group of hosts). As a result, for a host that belongs to a config group, all parameters are identical to their general configuration versions except those parameters that are changed via a config group.

In order to create a config group for a service, you should perform the following actions:

  1. Navigate to the subsection of the service (for example, HDFS) that is installed in the selected cluster, and select the Configuration groups tab.

    config groups 1
    Empty configuration groups list in the service subsection
  2. Click Create config group. The Create configuration group window opens. Enter the name of the new config group in the Configuration group name field. The Description field is optional. Click Next.

    config groups 2
    Create configuration group window
  3. In order to add hosts to the new config group, select the hosts and click Transfer selected.

    config groups 3
    Mapping window
  4. Click Save to save the mapping. The config group now contains hosts.

    config groups 4
    Host transfer
  5. In order to configure parameters of the new config group, click the new config group, select the parameters that you wish to configure differently, edit them, and click Save.

    config groups 5
    Configuration tab on the config group page

You can add all hosts where the service is installed to the new config group, yet then the configuration parameters also will be changed for all hosts. This can be done without creating a new config group using the general service configuration instead.

When creating and working with config groups you should consider the following:

  • Config group updates are synchronized with the general service configuration. The changes in the general service configuration are inherited in the config group (except those parameters that are changed).

  • It is not possible to add a single host into different config groups. Config groups of different objects don’t overlap. A single host may belong to different config groups when it relates to different objects.

  • Not all parameters are able to be changed via config groups. In such cases, the corresponding checkbox appears turned off.

You can create config groups for various ADCM objects. Config groups functionality is available for such objects as hostprovider, cluster, service, and component. For example, the components of the service that has a config group might be in their own config groups.
Found a mistake? Seleсt text and press Ctrl+Enter to report it