 |
Index for Section 8 |
|
 |
Alphabetical listing for C |
|
 |
Bottom of page |
|
caa_relocate(8)
NAME
caa_relocate - Relocates an application resource from one cluster member to
another
SYNOPSIS
/usr/sbin/caa_relocate resource_name [...] [-c cluster_member] [-q]
/usr/sbin/caa_relocate resource_name [-c cluster_member] [-q]
/usr/sbin/caa_relocate -s source_member [-c cluster_member] [-q]
PARAMETER
resource_name [...]
Name(s) of one or more application resources as specified in a resource
profile. If you do not specify any options, the caa_relocate command
relocates each specified application resource according to its
placement policy and required resource lists.
OPTIONS
-c cluster_member
Relocates each indicated resource to the specified member regardless of
its placement policy. If an application resource's required resources
are not available on the destination member, the caa_relocate command
fails and the resource remains on the current member.
-s source_member
Relocates all running application resources from the source_member. If
you do not also specify the -c option, the caa_relocate command
relocates each resource according to its placement policy and required
resource lists.
-q Runs the caa_relocate command in quiet mode; no messages are displayed
on the console.
DESCRIPTION
The caa_relocate command relocates application resources as directed by the
specified options and the resource profile. The specified resource must be
registered and running under CAA in the cluster environment before you can
relocate it. The command displays a message if you specify a cluster
member that is unavailable or the attempt to relocate failed.
You must have root privilege to use this command.
When you execute a caa_relocate command, CAA first issues a caa_stop
command for the application resource on the member on which it is currently
running. CAA then executes the caa_start command for the resource to start
it on a new member.
If CAA fails to stop the application resource on the current member, it
marks it as "Suspended." You cannot run caa_relocate on a suspended
resource. You must explicitly execute a second caa_stop command on the
resource and restart it with caa_start to return it to the "Running" state
before you reattempt to relocate it. If CAA fails to restart an application
resource, you may want to check the start section of the resource action
script.
If CAA fails to start the application resource on all other available
members, CAA tries to restart it on the current member. If it cannot
restart the application on the current member, it marks the application as
"Suspended."
The actions that CAA takes while relocating an application resource are
echoed on the command line and can also be monitored using EVM. See EVM(5)
for more information.
When relocating an application, if the communications path between the caad
daemons is busy, CAA will wait and retry the relocation when the caad
daemons are available.
EXAMPLES
The following example relocates an application resource to member
ferriswheel:
/usr/sbin/caa_relocate xclock -c polishham
Trying to start `xclock` on `polishham`
Successfully started `xclock` on `polishham`
The following example attempts to relocate all application resources from
member ferriswheel to member carousel:
/usr/sbin/caa_relocate -s provolone -c polishham
Trying to start `xclock` on `polishham`
Successfully Trying to start `xclock` on `polishham`
Successfully started `calc` on `polishham`
started `calc` on `polishham`
EXIT VALUES
The following exit values are returned:
0 Successful completion.
non-zero
A failure has occurred.
A corresponding text message will be given for the following error
conditions:
No root privilege.
Application is not running.
Cluster member intended for relocation is not available.
Relocation failed.
SEE ALSO
Commands: caa_profile(8), caa_register(8), caa_start(8), caa_stat(1),
caa_stop(8), caa_unregister(8)
Daemon: caad(8)
File: caa(4)
TruCluster Server Cluster Administration
 |
Index for Section 8 |
|
 |
Alphabetical listing for C |
|
 |
Top of page |
|