Auto-idling and oversubscribing behavior of data domains

Data domain profiles define two important aspects of data domain behavior — automatic idling and oversubscribing.

Automatic idling of data domains

A data domain profile may contain two settings:
  • auto-idle, which determines whether the data domain should be automatically turned to idle if it receives no queries during the timeout period. If set to false, the data domain is never turned idle. If set to true, the data domain turns idle if the idle-timeout period expires. The data domain is said to be idle when the Endeca Server stops the Dgraph process for it.
  • idle-timeout, which determines the optional timeout for automatically idling a data domain. If not specified, the default timeout of 10 minutes is used. The data domain that is set to automatically idle will be turned idle if, during this timeout period, it does not receive queries that can activate it.

You can use these data domain profile settings through the endeca-cmd put-dd-profile --auto-idle true/false --idle-timeout <min> command. Alternatively, you can use the putDataDomainProfile operation (and its idling options) of the Cluster Web Service.

Oversubscribing behavior of data domains

A data domain profile may contain a setting, oversubscribe that allows Endeca Server to oversubscribe resources while sharing them between this data domain and other data domains hosted by the Endeca Server.

This data domain profile setting is available through the endeca-cmd put-dd-profile --oversubscribe command. Alternatively, you can use the putDataDomainProfile operation (and its oversubscribing option) of the Cluster Web Service.

Typically, the system administrators of the Endeca Server cluster make decisions about which data domain profiles should be available for your use when you create data domains. For information on these settings and how they affect the behavior of data domains, see the Oracle Endeca Server Cluster Guide (which addresses the Endeca Server cluster administrators).