All Downloads are FREE. Search and download functionalities are using the official Maven repository.

en.help.ref-clusterinstances.html Maven / Gradle / Ivy

The newest version!

Clustered Server Instances

Use the Clustered Server Instances page to create and manage GlassFish Server instances in the current cluster.

The Cluster Name field is a read-only field that displays the name of the current cluster.

The Clustered Server Instances page displays a list of instances that are members of the current cluster. For each instance, the following information is provided.

Name

The name that was assigned to the instance when the instance was created. Clicking the name opens the General Information page for the instance.

LB Weight

An integer that represents the load-balancing weight of the instance.

The load-balancing weight determines the proportion of all requests to the cluster that the instance should process.

For example, in a two-instance cluster, you might require one instance to process one out of four requests, and the other instance to process three out of four requests. In this situation, set the weight of the instance that is process one out of four requests to 1 and set the weight of the other instance to 3. If you prefer to use percentages, set the weights of the instances to 25 and 75 respectively.

The default weight is 100.

Configuration

The configuration that the instance references. Clicking the configuration opens the Configurations page for the instance.

Node

The name of the node on which the instance resides. Clicking the name opens the Edit Node page for the node.

Status

An indication of whether the instance is running, requires restart to be updated with configuration changes, or is not running. This field is read only.

The Server Instances table also contains the following options.

New

Button to add an instance to the cluster.

Delete

Button to remove one or more selected instances from the cluster.


Caution - If you are using a Java Message Service (JMS) cluster with a master broker, do not delete the instance that is associated with the master broker. If this instance must be deleted, use the change-master-broker(1) subcommand to assign the master broker to a different instance.


Start

Button to start one or more selected instances in the cluster.

Stop

Button to stop one or more selected instances in the cluster.

Related Tasks
Equivalent asadmin Subcommands
Copyright © 2005, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices




© 2015 - 2024 Weber Informatics LLC | Privacy Policy