On Dec 5, 2007, at 1:44 PM, Dejan Muhamedagic wrote:
Hi,
On Wed, Dec 05, 2007 at 11:51:20AM +0100, Franck Ganachaud wrote:
Well I don't want hearbeat to stop or start mysql.
You should be better off if you do. Otherwise, you'll probably
end up with an unmaintainable and complex configuration.
And if I colocate R1 with mysql, will a R1 move from server A to B
implie mysql move also?
Not necessarily. Colocations don't have to be symmetrical.
particularly not if its a clone (ie. a resource that has a copy
running on each node)
if you really object to having heartbeat manage mysql, use
is_managed=false for just the mysql resource.
with this setting, the cluster will never ever modify the state of
your resource (only check it's health and make decisions for R1 based
on that)
Thanks,
Dejan
Franck.
Andrew Beekhof a ?crit :
On Dec 5, 2007, at 9:42 AM, Franck Ganachaud wrote:
I try to be more explicit.
I use v2 configuration
I got 2 servers A and B. A set (group) of resource R1.
R1 is running by default on server A and jump to server B in case
of
trouble.
This is currently setup and working fine.
Now, i need to check mysql running on both server A and B.
If mysql isn't ok on server running R1, I need to stop
whateverdaemond and move R1 to the other server
If mysql isn't ok on server not running R1, I just need to stop
whateverdaemond.
I made a OCF agent that does the "stop whateverdaemond if mysql is
down" job
dont do that
write a proper agent for whateverdaemond (maybe you can use an
init-script instead)
add a clone resource for mysql
add a clone resource for whateverdaemond
colocate whateverdaemond with mysql
colocate R1 with mysql
This where I get puzzled, how to translate the relation between the
"if running R1" and the agent I wrote it in heartbeat groups and
constraints
Hope it's clearer.
Franck.
Dejan Muhamedagic a ?crit :
Hi,
On Tue, Dec 04, 2007 at 05:25:08PM +0100, Franck Ganachaud wrote:
Hi,
I have a two 2 node cluster.
group1 is active/passive set of ressource.
group1 is currently hop-ing from one node to the other as
intended
when one of the group ressource isn't available.
Now I have a second task for heartbeat.
On each node, I have a mysql server, if it goes wrong, I must
shutdown a service and migrate the group1 (if it runs on this
node)
to the other node.
And this something I don't know how to do.
I was thinking about creating a group2 in an active/active
configuration testing mysql and if goes wrong just shutdown the
service in the stop process of the group2 but I don't know how to
force in this case the push of the group1 to the other node of
it's
running on the group2 failing node.
Sorry, but I can't follow. Can you please rephrase.
Which configuration do you use: v1 or v2?
Thanks,
Dejan
Any one can help me?
Hope it's clear.
Franck.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
--
GANACHAUD Franck
Consultant
Tel. : +33 (0)2 98 05 43 21
http://www.altran.com
--
Technop?le Brest Iroise
Site du Vernis - CS 23866
29238 Brest Cedex 3 - France
Tel. : +33 (0)2 98 05 43 21
Fax. : +33 (0)2 98 05 20 34
e-mail: [EMAIL PROTECTED]
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
--
GANACHAUD Franck
Consultant
Tel. : +33 (0)2 98 05 43 21
http://www.altran.com
--
Technop?le Brest Iroise
Site du Vernis - CS 23866
29238 Brest Cedex 3 - France
Tel. : +33 (0)2 98 05 43 21
Fax. : +33 (0)2 98 05 20 34
e-mail: [EMAIL PROTECTED]
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
