Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux-HA: Pacemaker

slow node discovery for pacemaker and heartbeat

 

 

Linux-HA pacemaker RSS feed   Index | Next | Previous | View Threaded


benzwt at gmail

Apr 23, 2012, 2:22 AM

Post #1 of 3 (512 views)
Permalink
slow node discovery for pacemaker and heartbeat

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

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


benzwt at gmail

Apr 23, 2012, 2:33 AM

Post #2 of 3 (487 views)
Permalink
Re: slow node discovery for pacemaker and heartbeat [In reply to]

sorry, I forget to provide the crm configure.
Here is the crm configurations

node $id="53ef725b-dc9a-42f2-ac02-8e41197bfeca" ubuntu85
node $id="59992f5b-12ca-4a84-adad-176b236ccb22" ubuntu84
primitive mfsmaster ocf:heartbeat:proftpd \
op monitor interval="30s" timeout="30s"
primitive mfsmaster_drbd ocf:linbit:drbd \
params drbd_resource="r0" drbdconf="/etc/drbd.conf" \
meta migration-threshold="10" \
op monitor interval="30s" timeout="20s"
primitive mfsmaster_fs ocf:heartbeat:Filesystem \
params device="/dev/drbd0" directory="/opt" fstype="ext4"
primitive mfsmaster_vip ocf:heartbeat:IPaddr2 \
params ip="10.0.0.89" nic="eth0:0"
group mfsmaster_group mfsmaster_fs mfsmaster_vip mfsmaster
ms mfsmaster_drbd_ms mfsmaster_drbd \
meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" notify="True"
colocation mfsmaster_colo inf: mfsmaster_group mfsmaster_drbd_ms:Master
order mfsmaster_order inf: mfsmaster_drbd_ms:promote mfsmaster_group:start
property $id="cib-bootstrap-options" \
dc-version="1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd" \
cluster-infrastructure="Heartbeat" \
expected-quorum-votes="2" \
stonith-enabled="false" \
no-quorum-policy="ignore" \
start-failure-is-fatal="false"

thanks!


On Mon, Apr 23, 2012 at 5:22 PM, benzwt benzwt <benzwt [at] gmail> wrote:
> 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

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org


andrew at beekhof

Apr 26, 2012, 7:02 PM

Post #3 of 3 (473 views)
Permalink
Re: slow node discovery for pacemaker and heartbeat [In reply to]

On Mon, Apr 23, 2012 at 7:22 PM, benzwt benzwt <benzwt [at] gmail> wrote:
> 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 ?

initdead probably.
also try man crmd and look for dc-deadtime

>
> 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
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Linux-HA pacemaker RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.