[ClusterLabs] Q: "migrating a clone" with crm shell
kgaillot at redhat.com
Tue Jun 2 09:41:45 EDT 2015
On 06/02/2015 03:02 AM, Ulrich Windl wrote:
> I have a globally-unique="false" interleave="true" clone running on two nodes. For a software upgrade I want to disable the rsource on the node to be updated. There fore I tried "crm resource migrate my_clone PT10M", which did not work:
> Resource 'my_clone' not moved: active in 2 locations.
> You can prevent 'my_clone' from running on a specific location with: --ban --host <name>
> Error performing operation: Invalid argument
globally-unique="false" means that all clone instances are equivalent,
and only one instance is ever needed on any one node. So there's no
logical meaning to migrating such a clone. You can stop it on any node
any time (e.g. by putting the node in standby, which you'd probably do
for an upgrade anyway).
If each clone instance handles a different range of input, so that more
than one instance can run on a single node, then you want
> I couldn't quite find out what the right command should be, especially as the "help migrate" says:
> crm(live)resource# help migrate
> Migrate a resource to a different node. If node is left out, the
> resource is migrated by creating a constraint which prevents it from
> running on the current node. Additionally, you may specify a
> lifetime for the constraint---once it expires, the location
> constraint will no longer be active.
> migrate <rsc> [<node>] [<lifetime>] [force]
> I tried " crm resource migrate --ban --host active_node_name my_clone PT10M", but that triggers a syntax error:
> usage: migrate <rsc> [<node>] [<lifetime>] [force]
> How should I "temporarily shutdown" the resource of the clone on one node?
> Users mailing list: Users at clusterlabs.org
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
More information about the Users