Depending on which version of the pingd RA you have, you can set the "options" parameter with any additional pingd flags you need.
In the pacemaker-1.0 edition of pingd, you can set: -i N (re-ping interval) -n N (number of ping attempts per host before declaring it dead) -t N (ping timeout in seconds) On Thu, Dec 4, 2008 at 16:35, Joerg Streckfuss <[email protected]> wrote: > >> IPaddr does not check reachability in the net. >> There is a parameter in the ha.cf called deadping. It is 30s by default. So >> changes in the reachability take 30s + damping time to get active. Set this >> paramter to 10s (or lower) according to your needs. You will have to restart >> heartbeat. >> >> Greetings, > > Hi, I tested to set the value of 'deadping' to 3 with a 'dampen' value of 1 > > ha.cf: > > <snip> > initdead 30 > deadtime 2 > keepalive 800ms > warntime 1800ms > deadping 3 > </snip> > > xml snippet for resource pingd: > > <clone id="clone-pingd"> > <meta_attributes id="clone-pingd-meta-attrs"> > <nvpair id="clone-pingd-meta-attr-clone-max" name="clone_max" value="2"/> > <nvpair id="clone-pingd-meta-attr-clone-node-max" name="clone_node_max" > value="1"/> > </meta_attributes> > <primitive id="pingd" class="ocf" type="pingd" provider="heartbeat"> > <operations> > <op id="op-pingd" name="monitor" interval="1s" timeout="1s"/> > </operations> > <instance_attributes id="pingd-inst-attrs"> > <nvpair id="pingd-inst-attr-multiplier" name="multiplier" > value="200"/> > <nvpair id="pingd-inst-attr-dampen" name="dampen" value="1s"/> > <nvpair id="pingd-inst-attr-host-list" name="host_list" > value="default-gateway switch1 switch2"/> > </instance_attributes> > </primitive> > </clone> > > But the cluster still behaves as before. After the master node lost its > connection to one ping node, the failover occurs at least 70 seconds later. > > In addition it would be great to reduce the ping testing interval. it still > sticks at 10 seconds. As you can see I tried to set it to one seconds. > > When i look into meta-data of ocf-RA pingd i can found this entries: > > <actions> > <action name="start" timeout="90" /> > <action name="stop" timeout="100" /> > <action name="monitor" depth="0" timeout="20" interval="10" start-delay="1m" > /> > <action name="meta-data" timeout="5" /> > <action name="validate-all" timeout="30" /> > </actions> > > I guess the op attribute 'interval' means something like pingd test interval, > right? > > As far as I can remember in heartbeat version 2.1.4 the default test interval > for pingd was 1 second. > > Greetings, > > Joerg > > -- > Dipl.-Ing. (FH) Joerg Streckfuss, Phone: +49 40 808077-631 > > DFN-CERT Services GmbH, https://www.dfn-cert.de/, Phone +49 40 808077-555 > Sitz / Register: Hamburg, AG Hamburg, HRB 88805, Ust-IdNr.: DE 232129737 > Sachsenstraße 5, 20097 Hamburg/Germany, CEO: Dr. Klaus-Peter Kossakowski > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
