Lars Marowsky-Bree escribió:
On 2007-07-12T18:08:17, Adrian Chapela <[EMAIL PROTECTED]> wrote:
I am looking for a configuration to monitoring a resource. I want to
know if resource is running OK. I don't want start, stop, restart,
reload a resource with heartbeat, I only want to monitoring it... and
takeover if necessary.
You're contradicting yourself.
Yes, with is_managed, heartbeat will not stop/start/restart/reload the
resource, but monitors will be setup.
OK, this is I want.
No, with is_managed it will not perform takeover, because you said you
didn't want the resource to be started/restarted/stopped.
What is it that you really want to achieve? ;-) Give us the use case,
not the desired implementation.
My desired implementation is:
- Two node MySQL Server. Replication Master to Slave (Two must be
running at same time).
- One VIP to connects to the Master and when the master goes down, the
VIP must be assigned to the slave Node.
- The VIP transition must do in network failure or MySQL master failure.
- When Master goes up again, the VIP can't be assigned to it again. An
administrator take this decision later.
Now to make takeover I assign a value to an attribute wich will be look
in a rule to change the score, as same as pingd rule of the howto's, but
In some cases Heartbeat reloads the service MySQL, and this is a
problem, because my server take a lot of time to be up (more than 100
seconds).
Can you help me ??
Regards,
Lars
Best regards,
Adrián.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
