On 2009-05-25 17:18, Juha Heinanen wrote: > Florian Haas writes: > > > 1. Set rrp_problem_count_timeout and/or rrp_problem_count_threshold > > ridiculously high so the ring status never goes to faulty. (It seems > > that RRP "problem counting" can't be disabled altogether). > > > > 2. Have package maintainers include some magic that does > > "openais-cfgtool -r" every time a network link changes its status to UP > > (where the network management subsystem permits this). > > > > 3. Instruct users to install cron jobs that do "openais-cfgtool -r" in > > specified intervals, causing OpenAIS to re-check the link status > > periodically. > > all the above sound like hacks to me. a better solution is to have a > crm variable that tells if automatic recovery is desired.
Agree that they're hacks, but disagree with your alternative. Why should Pacemaker be concerned with low-level OpenAIS recovery procedures? Florian _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker