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.

The following example ensures the following:
  • The Endeca Server machines hosting the data domain cluster are oversubscribed, meaning they are set to share their CPU capacity with more than one data domain cluster hosted on these machines, even if the total capacity required by these data domains exceeds the amount of CPU on each Endeca Server node. This behavior is defined by the allowOversubscribe element in the data domain profile definition that must be set to true.
  • The data domain cluster's leader node shares the query load with the other nodes and is not dedicated to only processing updating requests. This behavior is defined by the allowQueriesOnLeader element in the data domain profile definition that must be set to true.

Example

This example illustrates the data domain profile for data domain clusters with low hardware usage requirements. Because it represents a snippet of a full web service request, the example does not list the namespace of the Cluster Web Service or the operation used to define the profile.

The example specifies the number of follower nodes as 1. This number is arbitrary — you can modify it according to the needs of your data domain and the overall capacity of nodes in the Endeca Server cluster.

The important parts of this example are the settings for allowQueriesOnLeader and allowOversubscribe, which are both set to true: 
<dataDomainProfile>
    <name>low hardware-usage profile</name>
    <description>Profile for a data domain with low hardware usage</description>
    <allowQueriesOnLeader>true</allowQueriesOnLeader>
    <numFollowers>1</numFollowers>
    <readOnly>false</readOnly>
    <allowOversubscribe>true</allowOversubscribe>
    <numComputeThreads>2</numComputeThreads>
    <computeCacheSizeMB>1</computeCacheSizeMB>
    <startupTimeoutSeconds>600</startupTimeoutSeconds>
    <shutdownTimeoutSeconds>30</shutdownTimeoutSeconds>
    <sessionIdType>header</sessionIdType>
    <sessionIdKey>X-Endeca-Session-ID</sessionIdKey>
</dataDomainProfile>