<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="para">Hello,<br>
<br>
my problem is closely related to the thread [1], but I didn't find
a solution there. I have a resource that is set up as a clone C
restricted to two copies (using the clone-max=2 meta attribute<code></code>),
because the resource takes long time to get ready (it starts
immediately though), and by having it ready as a clone, I can
failover in the time it takes to move an IP resource. I have a
colocation constraint "resource IP with clone C", which will make
sure IP runs with a working instance of C:<br>
<br>
Configuration:<br>
Clone: dummy-clone<br>
Meta Attrs: clone-max=2 interleave=true <br>
Resource: dummy (class=ocf provider=heartbeat type=Dummy)<br>
Operations: start interval=0s timeout=20
(dummy-start-interval-0s)<br>
stop interval=0s timeout=20
(dummy-stop-interval-0s)<br>
monitor interval=10 timeout=20
(dummy-monitor-interval-10)<br>
Resource: ip (class=ocf provider=heartbeat type=Dummy)<br>
Operations: start interval=0s timeout=20 (ip-start-interval-0s)<br>
stop interval=0s timeout=20 (ip-stop-interval-0s)<br>
monitor interval=10 timeout=20
(ip-monitor-interval-10)<br>
<br>
Colocation Constraints:<br>
ip with dummy-clone (score:INFINITY)<br>
<br>
State:<br>
Clone Set: dummy-clone [dummy]<br>
Started: [ sub1.example.org sub3.example.org ]<br>
ip (ocf::heartbeat:Dummy): Started sub1.example.org<br>
<br>
<br>
This is fine until the the active node (sub1.example.org) fails.
Instead of moving the IP to the passive node (sub3.example.org)
with ready clone instance, Pacemaker will move it to the node
where it just started a fresh instance of the clone
(sub2.example.org in my case):<br>
<br>
New state:<br>
Clone Set: dummy-clone [dummy]<br>
Started: [ sub2.example.org sub3.example.org ]<br>
ip (ocf::heartbeat:Dummy): Started sub2.example.org<br>
<br>
<br>
Documentation states that the cluster will choose a copy based on
where the clone is running and the resource's own location
preferences, so I don't understand why this is happening. Is there
a way to tell Pacemaker to move the IP to the node where the
resource is already running?<br>
<br>
Thanks!<br>
Jan Wrona<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://lists.clusterlabs.org/pipermail/users/2016-November/004540.html">http://lists.clusterlabs.org/pipermail/users/2016-November/004540.html</a><br>
</div>
</body>
</html>