[ClusterLabs] Corosync CPU load slowly increasing if one node present
stefan.lists at gmx.net
Thu Apr 27 04:13:33 EDT 2017
I am using Pacemaker (1.1.12), Corosync (2.3.0) and libqb (0.16.0) in 2-node clusters (virtualized in VMware infrastructure, OS: RHEL 6.7).
I noticed that if only one node is present, the CPU usage of Corosync (as seen with top) is slowly but steadily increasing (over days; in my setting about 1% per day). The node is basically idle, some Pacemaker managed resources are running but they are not contacted by any clients.
I upgraded a test stand-alone node to Corosync (2.4.2) and libqb (1.0.1) (which at least made the memleak go away), but the CPU usage is still increasing on the node.
When I add a second node to the cluster, the CPU load drops back down to a normal (low) CPU usage.
I haven't witnessed the increasing CPU load yet if two nodes were present in a cluster.
Even if running Pacemaker/Corosync as a massive-overkill-Monit-replacement is questionable, the observed CPU-load is not what I expect to happen.
What could be the reason for this CPU-load increase? Is there a rational behind this?
Is this a config thing or something in the binaries?
# Please read the corosync.conf.5 manual page
# Security configuration
# Timeout for token
# Number of messages that may be sent by one processor on receipt of the token
# How long to wait for join messages in the membership protocol (ms)
# Turn off the virtual synchrony filter
# Stagger sending the node join messages by 1..send_join ms
# Limit generated nodeids to 31-bits (positive signed integers)
# Interface configuration
More information about the Users