[Linux-HA] Constraint Listing /
RestartAfterSuccessfulRecovery constraint?
Andrew Beekhof
beekhof at gmail.com
Mon Oct 16 01:58:06 MDT 2006
On 10/15/06, Serge Dubrouski <sergeyfd at gmail.com> wrote:
> Combine your resources into a group. Database fist and then resources
> that depend on it. In this case restart of the database will cause
> restart of the resources.
One can also use ordering constraints combined with restart_type.
<quote>
restart_type
Used when the other side of an ordering dependency is restarted/moved.
* ignore : the default. Don't do anything extra.
* restart : Use this for example to have a restart of your database
also trigger a restart of your web-server.
</quote>
>
> On 10/15/06, Robert Heinzmann <Robert.Heinzmann at gmx.net> wrote:
> > Hello,
> >
> > is there a listing of all constraints available in Heartbeat on the web ?
> >
> > I'm looking for a kind of "Restart after failed" constraint. This should
> > restart resources (A) after a successful restart of a resource (B). Lets
> > say B is a database and A is an application, there are applications that
> > fail to reconnect to the database. In those cases a restart of the
> > application may be required AFTER the database has successfully
> > restartet. Is there such a constraint available in Heartbeat 2 ?
> >
> > Regards,
> > Robert
> > _______________________________________________
> > Linux-HA mailing list
> > Linux-HA at lists.linux-ha.org
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > See also: http://linux-ha.org/ReportingProblems
> >
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
More information about the Linux-HA
mailing list