Sets or displays pool status.
You can also use OpenSwitch Manager to change the pool
status.
rp_pool_status [pool_name, status]
Name of the pool to be displayed or changed.
The status to which the pool is to be changed. If you supply a status value, but no pool name, the status of all pools is changed. Table 7-10 describes the values for status.
Status |
Description |
|---|---|
PRE_UP |
Mutually-aware-specific pool status. The pool is either in the process of being marked as UP, or has encountered a problem during that process. Check the error log to troubleshoot the problem. After you resolve the problem, manually set the pool status to UP on one of the mutually-aware companion OpenSwitch servers. The command will be propagated to the other OpenSwitch companion if it is running. WARNING! Do not manually set a pool’s status to PRE_UP. |
UP |
The pool is immediately available for use. |
PRE_DOWN |
Mutually-aware specific pool status. The pool is either in the process of being marked as DOWN, or has encountered a problem during that process. Check the error log to troubleshoot the problem. After you resolve the problem, manually set the pool status to DOWN on one of the mutually-aware companion OpenSwitch servers. The command will be propagated to the other OpenSwitch companion if it is running. WARNING! Do not manually set a pool’s status to PRE_DOWN. |
DOWN |
The pool is unavailable, and is not considered for use by any new client connections established to OpenSwitch. |
PRE_LOCKED |
Mutually-aware specific pool status. The pool is either in the process of being marked as LOCKED, or has encountered a problem during that process. doing so. Check the error log to troubleshoot the problem. After you resolve the problem, manually set the pool status to LOCKED on one of the mutually-aware companion OpenSwitch servers. The command will be propagated to the other OpenSwitch companion if it is running. WARNING! Do not manually set a pool’s status to PRE_LOCKED. |
LOCKED |
The pool is available, but any new incoming connections actively being connected through the pool are blocked (or stopped) until the status is changed to UP or DOWN. Blocked connections appear to the client applications to have stopped responding until the pool is unlocked. |
SUSPENDED |
The pool is being suspended by OpenSwitch due to a failure that requires an administrator’s manual intervention. See “Invoking custom and manual scripts” for more information. The pool blocks on all new connections until rp_go is issued. WARNING! Do not manually set a pool’s status to SUSPENDED. |
Displays the list of all pools and their current status:
1> rp_pool_status 2> go
Returns:
pool_name status ------------- --------- POOL_A UP POOL_B UP POOL_C UP
Displays the current status of POOL_A:
1> rp_pool_status "POOL_A" 2> go
Returns:
pool_name status ------------- --------- POOL_A UP
Changes the status of POOL_A to LOCKED and displays the results:
1> rp_pool_status "POOL_A", "LOCKED" 2> go
Returns:
pool_name status ------------- --------- POOL_A LOCKED
Changing the status of a pool does not affect users that are currently using the pool.
Changing the status of a pool has no affect on existing connections.
If you do not have a pool-based server, use rp_server_status to set and check a server’s status.
If you have a pool-based server, use rp_pool_server_status to set and verify the server’s status.
rp_server_status displays the status of a server only if that server is listed in the [SERVER] section of the OpenSwitch configuration file, which may not be the same as a pool’s actual server status.
Connections that are currently blocked on a LOCKED pool continue to remain blocked until either the pool is unlocked or the client application disconnects. This means that any administrative requests made of the connection, such as a call to rp_switch, or rp_stop, are queued until the pool changes status.
Use rp_pool_status with the LOCKED argument, followed by a call to rp_stop, to display all activity on a pool.
If you issue rp_pool_status to set the pool status on a mutually-aware OpenSwitch server, the command is propagated to the companion OpenSwitch if it is running. The new pool status is also recorded in the mutually-aware configuration tables on the Adaptive Servers. If these steps fail, the pool status is reset to its original value and an error message is logged.
If FREEZE_CFG_ON_FAIL is enabled and the network fails between the local OpenSwitch server and the companion OpenSwitch server, you can use rp_pool_status only to display, not set, a pool’s status. This prevents the companion OpenSwitch servers from switching client connections to different Adaptive Servers while the network between OpenSwitch servers is not responding, which could cause data loss when replication is performed in only one direction. rp_pool_status allows you to reset the pool status when the network is restored between the companion OpenSwitch servers, or if FREEZE_CFG_ON_FAIL is disabled.
The pool name does not exist within OpenSwitch:
rp_pool_status: There is no such pool 'pool_name'.
To list the existing pools, use rp_pool_help.
A mutually-aware OpenSwitch server has detected a problem in the network with its companion, and has stopped all future status changes until the network is restored and the status of the companion can be verified:
rp_pool_status:Status cannot be set/changed until connectivity is restored with the companion OpenSwitch site or the FREEZE_CFG_ON_FAIL parameter is turned OFF.
rp_pool_create, rp_pool_help
