[Pacemaker] slow node discovery for pacemaker and heartbeat

benzwt benzwt benzwt at gmail.com
Mon Apr 23 09:22:51 UTC 2012


Hi pacemakers,

I'm running two nodes on a subnet.

I opened a session to node A, B.
Then, I issued "service heartbeat start" on both nodes.
On the console of node A, I issued "crm_mon" to monitor the discovery
process. However, It took about 30s to show up that both nodes are
on-line.

Is there any setting I have to configure ?

I use
          pacemaker-1.0.0.8
          heartbeat-1.3.0.3
          #I didn't install corosync

the Ips for A, B are 10.0.0.84 and 10.0.0.85, respectively.

the ha.cf is as follows:

logfile /var/log/ha-log
autojoin none
node ubuntu84 ubuntu85
user_logd on
keepalive 2
deadtime 10
warntime 5
initdead 10
ucast eth0 10.0.0.85 # on host A
ucast eth0 10.0.0.84 # on host B
autofailback on
respawn hacluster /usr/lib/heartbeat/ipfail

best regards,
benzwt




More information about the Pacemaker mailing list