[/map {"- map/map "}) [/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) Managing Data Domain Profiles (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Managing Data Domain Profiles (linktext][/map/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This section describes how to create and manage profiles for data domains in the Endeca Server cluster.It also lists data domain profile parameters. (shortdesc] (topicmeta][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) About the data domain profile (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) About the data domain profile (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) 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). (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Deciding which data domain profile to use (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Deciding which data domain profile to use (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You can define several data domain profiles, each serving a typical service use case.In addition, a default data domain profile exists. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Data Domain profile parameters (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Data Domain profile parameters (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) 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. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Default data domain profile (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Default data domain profile (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This topic lists parameters for the default data domain profile used for single-node data domain deployments hosted by a single Endeca Server instance. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Defining a data domain profile (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Defining a data domain profile (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) 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. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Listing data domain profiles (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Listing data domain profiles (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Custom data domain profiles are created by an administrator in charge of the Endeca Server cluster.データ・ドメインを作成する前に、以前に定義したデータ・ドメイン・プロファイルの名前と特性を把握しておく必要があります。This information is returned with the operations from the Manage Web Service and Cluster Web Service, or with endeca-cmd. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Removing a data domain profile (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Removing a data domain profile (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You remove a data domain profile with endeca-cmd delete-dd-profile, or with the deleteDataDomainProfile operation of the Cluster Web Service. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) How idling affects data domain behavior (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) How idling affects data domain behavior (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) 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.データ・ドメインの自動アイドル化は、Endeca Serverデプロイでデータ・ドメインの増大を制御するのに有効で、これによりEndeca Serverクラスタのハードウェア使用率が向上します。This topic discusses how Endeca Server manages automatic idling of data domains. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) How oversubscribing affects hardware utilization (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) How oversubscribing affects hardware utilization (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) 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. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Example: data domain profile with low hardware usage (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Example: data domain profile with low hardware usage (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) This example illustrates the characteristics of the data domain profile that defines data domain clusters with low hardware usage requirements. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Example: data domain profile with high hardware usage (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Example: data domain profile with high hardware usage (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) 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. (shortdesc] (topicmeta] (topicref] (topicref] (map]