[Pacemaker] pacemaker and spanning tree in the network between the nodes

[hj lee]

On Wed, Dec 23, 2009 at 8:34 AM, Dejan Muhamedagic <dejanmm at fastmail.fm>wrote:

>
> > > > 3. Why the pingd attribute was not set immediately after pingd
> started
> > > > up, and was able to ping the ping node. After the pingd was started,
> then
> > > > it waited 60 seconds (the timeout value) to set the attribute so that
> > > > then the XEN resources were able to start, due to their location
> > > > constraint.
> > I must have observed this somehow falsely. The pingd attribute was set
> only
> > some seconds after the pingd was started on the nodes. However, the
> depending
> > XEN resources, were only started about a minute after that happend.
> > Is there any parameter I can use to shorten that time frame from a minute
> to
> > some seconds?
>
> Don't think so. I don't understand why it waited.
>

The pingd resource has "dampen" instance parameter. The pingd udpate is
delayed by dampen time. The default value is 1 sec. Unless you set it to
60s, it should update every 1 sec. I think something is wrong in your case.
The pingd is working fine in my system.

Thanks
hj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20091224/22e26ba0/attachment-0001.htm>