Managing Data Domain Profiles

This section describes how to create and manage profiles for data domains in the Endeca Server cluster. It also lists data domain profile parameters.

About the data domain profile
The data domain profile is a collection of characteristics that the Endeca Server uses to create a data domain. Before you can create a data domain, you must create a data domain profile (or use the default profile).
Deciding which data domain profile to use
You can define several data domain profiles, each serving a typical service use case. In addition, a default data domain profile exists.
Data Domain profile parameters
The endeca-cmd put-dd-profile command, or the Cluster Web Service putDataDomainProfile operation, let you configure a data domain profile and its parameters. This topic lists these parameters and provides their descriptions.
Default data domain profile
This topic lists parameters for the default data domain profile used for single-node data domain deployments hosted by a single Endeca Server instance.
Defining a data domain profile
To define a new data domain profile in the Endeca Server, use the endeca-cmd put-dd-profile command, or the putDataDomainProfile request of the Cluster Web Service. The domain profile must exist before you create data domains, otherwise, the default data domain profile is used.
Listing data domain profiles
Custom data domain profiles are created by an administrator in charge of the Endeca Server cluster. Before you create a data domain, you need to know the names and characteristics of previously defined data domain profiles. This information is returned with the operations from the Manage Web Service and Cluster Web Service, or with endeca-cmd.
Removing a data domain profile
You remove a data domain profile with endeca-cmd delete-dd-profile, or with the deleteDataDomainProfile operation of the Cluster Web Service.
How idling affects data domain behavior
You can create a data domain profile that automatically turns a data domain to idle if it receives no queries for the specified timeout period. Automatic idling of data domains is useful as it helps control the proliferation of data domains in the Endeca Server deployment, thus improving hardware utilization by the Endeca Server cluster. This topic discusses how Endeca Server manages automatic idling of data domains.
How oversubscribing affects hardware utilization
Data domain profiles define the hardware resources that the Endeca Server cluster makes available to the data domains it hosts. This topic explores the interaction between oversubscribing of data domains and hardware utilization.
Example: data domain profile with low hardware usage
This example illustrates the characteristics of the data domain profile that defines data domain clusters with low hardware usage requirements.
Example: data domain profile with high hardware usage
This example illustrates the characteristics of a data domain profile that defines a production-grade data domain cluster. In such a cluster, each Dgraph node runs on a dedicated Endeca Server node, and a dedicated leader node handles only updating requests.