Use this page to view configurations of existing dynamic clusters. To view this administrative console page, click Servers > Dynamic clusters > dynamic_cluster_name.
Name | The name field is a required field and is not editable from this panel. The name for a dynamic cluster must be unique in the cell. |
Node group | This attribute refers to the affiliated node group, which is defined when creating a new dynamic cluster. A node group and a dynamic cluster are closely related. The node group is a user-defined affiliation of nodes that share a common property. A dynamic cluster is a cluster of servers within a node group, whose members, server instances, reside on a node within a node group, and are application deployment targets. |
Number of running instances | This field is automatically generated based on the number of instances running for each dynamic cluster. For example, a dynamic cluster might have three applications deployed on it, with two instances running on each of the four members of the dynamic cluster. In this example, 8 is displayed. |
Operational mode | You can set this field to one of three values: automatic, supervisory, or manual to indicate the mode which the dynamic cluster operates in. Automatic mode is the equivalent of on demand mode. This mode allows the dynamic operations environment to handle placements and provisioning. Supervisory mode is a combination of administering by dynamic operations and the system administration. The WebSphere Extended Deployment environment makes recommendations to the administrator, which the administrator can implement or disregard. Manual mode indicates no interaction from the dynamic operations environment. You can change the operational mode in the administrative console by clicking Servers > Dynamic clusters. |
Minimum number of cluster instances | Each entry must contain a set number of minimum running instances for a dynamic cluster. If a minimum value is excessive, performance degradation might occur. To stop instances when there is no activity, select Stop all instances started during periods of inactivity and type the Time to wait before stopping instances in minutes. This is the default option. If you want one cluster instance started at all times, select Keep one instance started at all times. To have multiple cluster instances started at all times, select Keep multiple instances started at all times and type the Number of instances that you want started at all times. |
Maximum number of instances | If you want to limit the number of cluster instances, select Limit number of cluster instances that can start and type the maximum Number of instances. If you want no limit on the number of cluster instances, select Do not limit the number of instances that can start. |
Vertical stacking of instances on node | Enable vertical stacking to improve bottleneck conditions between applications by selecting Allow more than one instance to start on the same node, and typing the Number of instances. The number of instances is the number of application servers for a cluster that are needed to use all the power of a node. Also, the number you choose for vertical stacking is the number of servers automatically created. |