disable-http-lb-server

This subcommand has been retained from Oracle GlassFish’s original integration with external load balancers, but it has no proper integration functionality in Payara Server. Hence, it is not intended to be used in any way.
The documentation in this page may not be accurate.

Disables a server or cluster managed by a load balancer.

Synopsis

asadmin [asadmin-options] disable-http-lb-server [--help]
[--timeout 30]
target
shell

Description

The disable-http-lb-server subcommand disables a standalone server or cluster of servers for load balancing. The disabled server instance or cluster goes offline for load balancing with a minimum impact to users.

Once the target has been disabled and the changes have been applied to the load balancer, the load balancer stops assigning new requests to the target. Session requests with sessions created before disabling the target continue to be assigned to that target until the timeout is reached. This process is known as quiescing.

Changes are applied the load balancer automatically. You can also manually export the configuration using export-http-lb-config and copy it to the load balancer.

Options

asadmin-options

Options for the asadmin utility. For information about these options, see the asadmin help page.

--help
-?

Displays the help text for the subcommand.

--timeout

The timeout (in minutes) to wait before disabling the specified target. This time allows for the graceful shutdown (quiescing) of the specified target. The default value is 30 minutes. The minimum value is 1 minute.

Operands

target

This operand specifies which server instances and clusters to disable. Valid values are:

  • cluster_name - The name of a target cluster.

  • instance_name - The name of a target server instance.

Examples

Example 1 Disabling a Cluster for Load Balancing

This example disables load balancing for a cluster named mycluster.

asadmin> disable-http-lb-server mycluster

Command disable-http-lb-server executed successfully.
shell

Exit Status

0

subcommand executed successfully

1

error in executing the subcommand

See Also