Re: VRRPv3 support in Keepalived
"Paul Robert Marino" <[email protected]>
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <[email protected]> |
If you read the email again it is a single float which means it is backward compatible with current configurations because it will be read 1 as 1.0 in current configurations easily. I wrote a hach patch as a prof of concept a couple of years ago that was incompatible with current configs but knew it was possible. I just didn't have time to debug it in my project where I needed a 0.05 second interval. The hack patch has been in production for years now without a glitch. The trick is that the heartbeats are over bonded direct cables not through a switch and I use a monitor script that calls fping to check the upstream routers. However I would prefer to use something like Avaya's VLACP instead. -- Sent from my HP Pre3 ---------- On Nov 11, 2014 7:48 PM, Lennart Sorensen <[email protected]> wrote: On Tue, Nov 11, 2014 at 07:07:03PM -0500, Paul Robert Marino wrote: > No it does not if you read the RFC it specifies "centiseconds" that's 1 100th of a second.<br>Most implementations don't fully support it because its very CPU intensive but it is in the RFC.<br><br><br><span style="font-family:Prelude, Verdana, san-serif;"><br><br></span><span id="signature"><div style="font-family: arial, sans-serif; font-size: 12px;color: #999999;">-- Sent from my HP Pre3</div><br></span><span style="color:navy; font-family:Prelude, Verdana, san-serif; "><hr align="left" style="width:75%">On Nov 11, 2014 6:55 PM, Lennart Sorensen <[email protected]> wrote: <br><br></span>On Tue, Nov 11, 2014 at 02:39:48PM -0500, Paul Robert Marino wrote: <br>> Alexandre <br>> <br>> Please ask them to make the interval a double float if you can. I <br>> actually have a legitimate business case in the broadcast video <br>> industry which requires this even though my test at an intervals of <br>> 0.02 and 0.01 used nearly an entire CPU core. <br> <br>But that violates the standard. <br> <br>-- <br>Len Sorensen <br> Well what is wrong with the current code just using an integer to store a value you send on the wire as an integer? No point getting floating point involved. That is why the VRRPv3 changed the units to centiseconds, rather than allowing decimal values. Well by current code I mean what was sent to the mailing list in the past as seen here: http://permalink.gmane.org/gmane.linux.keepalived.devel/4097 -- Len Sorensen ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ Keepalived-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/keepalived-devel