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, a data domain profile must exist.

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. You can change a data domain after it has been initially created based on the previously defined profile.

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 name, 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 Dgraph processes should be read-only; session affinity configuration; the hardware characteristics of Dgraph processes — the number or required CPU threads and the cache size; and, optionally, the arguments that are passed to the Dgraph processes for this profile.