>>> Dejan Muhamedagic <[email protected]> schrieb am 01.10.2013 um 19:09 in Nachricht <[email protected]>: > Hi, > > On Tue, Oct 01, 2013 at 05:01:52PM +0200, Moullé Alain wrote: >> Hi, >> >> with stack Pacemaker/corosync; >> >> suppose that a node in a HA cluster is so loaded (IOs, etc.) during >> more than the heartbeat timeout value but temporarily loaded, so >> loaded that it can't even no more manage heartbeat tokens, and it is >> fenced because he can't manage heartbeat tokens, whereis there is >> not a real problem, just a node temporarily overloaded. >> >> how do you/could we manage this type of problem ? >> is there a way to always give higher priority to the corosync >> traffic upon any other load ? > > The corosync process should be running at a higher priority > (i.e. close to real-time). Doesn't it?
Once we come to I/O, scheduling priorities help nothing. Really. > > Thanks, > > Dejan > >> Thanks >> Alain >> _______________________________________________ >> Linux-HA mailing list >> [email protected] >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
