On 7/27/07, Adrian Chapela <[EMAIL PROTECTED]> wrote: > For now this question is in the air... I sent my config, etc. And I > still have the same doubts.
sometimes they let me go on vacation > Andrew Beekhof escribió: > > On 7/18/07, Adrian Chapela <[EMAIL PROTECTED]> wrote: > >> Hello, > >> > >> I am reading list and documentation but I don't understand > >> resource_stickiness, default_resource_stickiness , > >> default_resource_failure_stickiness. > >> > >> I think that with default_resource_failure_stickiness I could do wich I > >> want. > >> > >> I want: > >> 1.- When a resource fails, moves to another best suitable node > >> 2.- When the "master node" comes up again, the failed resource must > >> be in the secondary node. > >> > > > > then you want: > > > > default_resource_failure_stickiness=-INFINITY (if it fails, move > > immediately), and > > > > default_resource_stickiness=INFINITY (dont move it unless it fails or > > the node is shutting down or similar) > > > > > >> To do that I configure in cib the next: > >> > >> default_resource_failure_stickiness=-INFINITY -> with this the resource > >> doesn't execute in any node. > > > > has it failed once on every node? > > you'll need to clear out the failcount before it will be allowed to > > run there again > How can I reset the failcount ?? crm_failcount --help > If I shutdown heartbeat and I startup > again, is it the same failcount ?? no. it will be zero again _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
