[Pacemaker] corosync, ocfs2_controld.pcmk insane?
Matthew O'Connor
matt at ecsorl.com
Fri May 11 14:19:26 UTC 2012
This might be the wrong place to ask this question, but between
corosync, OCFS2 and Pacemaker, under what circumstances would corosync
start consuming mass quantities of CPU? It started last night around
30%, and this morning is up around 110%. 40% is user, 47% system.
ocfs2_controld.pcmk is running at 50% CPU utilization. I've seen this
before on one of my other test-lab clusters, as though something is
spinlocking when there is a failure with some communication between the
(at present) two nodes. Indeed, last night I was testing some failover
cases, and the problem actually seemed to start after hard-rebooting one
of the members.
Using Pacemaker 1.1.5, Corosync 1.3.0, and ocfs2_controld (Aug 19 2011)
on Ubuntu Server 11.10 amd64.
Thanks!!
-- Matt
More information about the Pacemaker
mailing list