The node profile for the Endeca Server defines the hardware
characteristics that the Endeca Server cluster uses to create an Endeca Server
node.
The
node profile for the Endeca Server nodes defines:
- Number of CPU cores. This is
the number of CPU cores allocated to each Endeca Server instance in the
cluster. When the Endeca Server application is deployed in the WebLogic Server,
the number of CPU cores is determined automatically at startup. The default is
the larger of 2 or the number of available CPU cores on the node.
- The size of RAM in MB. The
default is 1024 MB. This is the size of RAM allocated to each Endeca Server
instance in the cluster.
Only one node profile can be configured in the system. It is used by all
Endeca Server instances (nodes) in the Endeca Server cluster.
The hardware characteristics specified in the node profile have the
following effect:
- When you initially deploy an
Endeca Server instance in the WebLogic Server, the default node profile
settings are used. In addition, depending on the choices you make during the
installation process, the HTTPS protocol can be used for communication between
the Endeca Server instances.
- Once the Endeca Server is
deployed in a WebLogic Server, you can change the hardware node profile by
running the command for changing it on any Endeca Server node. Once you change
it, it overrides the default node profile, and all nodes in the Endeca Server
cluster start using the new node profile.
Typically, administrators set the node profile to consume most if
not all available hardware resources on the nodes. For example, if a machine
has 12 CPUs, the node profile's
numCPUcores will be set to 12 also.
- Before changing the
hardware node profile, it is useful to obtain the current node profile. Use the
endeca-cmd get-node-profile command, or the
getNodeProfile operation of the Cluster Web Service.
Important: It is not recommended to change the node
profile after creating data domains, especially in cases when you reduce the
number of CPU cores or the size of RAM available to the nodes in the Endeca
Server cluster.