[Linux-HA] Automatic resource restart/clone resources

[Andrew Beekhof]

On 10/3/06, Max Hofer <max.hofer at apus.co.at> wrote:
> In the current configuration i have a cloned resource (one instance for each
> cluster node, 2 nodes in the cluster).
>
> The resource can not failover to the other node because it is an ISDN card
> which apparently can not be relocated. The application running on the cluster
> is a resource called APPL and depends on a running ISDN resource.
>
> Currently when an ISDN resource fails on one node it is stopped on this node
> and it is never restarted withouth manual intervention (setting failcount to
> 0 or using crm_resource -C).

try setting resource_failure_stickiness = 0 for just the ISDN resource

>
> I have following questions:
> * do i have to write a rule that a certain clone can only run on a certain
> node?

you cant do that at all.

are both ISDN connections ever active at the same time?  if not, you
probably shouldnt be using a clone.

> Or does clone_max, clone_node_max implicitely create those rules for
> me? What happens when i add an additional node with no ISDN card at a later
> stage?

By default, symmetric_cluster = true.  This means you have to use
rsc_location constraints to tell us where we CANT run the resources.

If you set that to false, then you need to use rsc_location
constraints to tell us where we _CAN_ run the resources.

The idea being that you only need to specify the exception(s).

> * Is there a way to tell the CRM to try a restart of the failed resource (X
> times before giving up)

If you mean "before giving up on node A", yes.  Thats what
resource_failure_stickiness is for.  The problem is you set it to
-INFINITY, which means X = 1.

>
> The bahevaiour i really would llike to have:
> * If the ISDN resource where APPL is runing fails, failover to the other node
> (if there runs the ISDN resource)

that would be automatic depending on your values of resource_failure_stickiness.

> * if the ISDN resource fails, try to restart it again periodcailly

a cron job resetting the failure count would achieve this

> can anyone give me a clue how to implement this?
>
> Attached a minimum CIB and the status after the monitor operaiton failed.
>
> kind regards
> Max
>
>
> _______________________________________________
> 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
>
>
>