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).

The profile serves as a template for the Endeca Server when it initially creates data domains and allocates resources to them, from the pool of provisioned Endeca Server instances.

A data domain profile defines the resources available to a data domain, such as the number of Dgraph nodes. It also defines the hardware utilization pattern the Endeca Server cluster will use when allocating its servers to the data domains using this profile.

A data domain profile is defined with the putDataDomainProfile operation of the Cluster Web Service, or using endeca-cmd put-dd-profile.

A data domain profile includes:

A data domain's name and description
The number of follower nodes required
Whether the leader is dedicated to updating requests or is sharing a regular query load
Whether the Endeca Server can oversubscribe its nodes while sharing them with other data domains
Whether the data domain should be auto-idled after a timeout
Whether the Dgraph processes should be read-only
Session affinity configuration
Hardware characteristics of Dgraph processes — the number or required CPU threads and the cache size
Optionally, the arguments passed to the Dgraph processes for this profile.

When you create a data domain, Endeca Server creates an internal .profile file associated with each new data domain and stores it in the index of the data domain. The file contains the configuration of the profile with which the data domain was created. If you later update the data domain, its .profile file is updated. When you export the data domain, the .profile file is exported, and when you import the data domain, this file is used as the data domain's profile for the new data domain.

The .profile file contains the data domain profile info, which is applied to the data domain. Its contents is similar to the following:

computeCacheSizeMB=0
sessionIdType=header
numFollowers=0
numComputeThreads=4
allowOversubscribe=true
shutdownTimeoutSeconds=30
startupTimeoutSeconds=600
args=
idleTimeoutMinutes=15
autoIdle=false
readOnly=false
description=this is a customized data domain profile
allowQueriesOnLeader=true
sessionIdKey=X-Endeca-Session-ID

Once an Endeca data domain is created, you only need to use the name of the data domain to manage it. You do not need to know which port the Dgraph processes for the data domain are running on, as the Endeca Server keeps track of that information using its Cluster Coordinator services. This name-only reference to the data domains makes it much easier to enable and disable them and perform other data domain management operations.