[Pacemaker] heartbeat keep alive latency questions

[Michael Schwartzkopff]

Am Sonntag, 6. April 2014, 11:29:02 schrieb Lev G:
> We use Corosync in CentOS 6.
> There are few questions:
> What is the highest network latency the Corosync can survive with its
> default configuration?
> How is possible to adjust the Corosync latency in high latency network
> infrastructure?
> 
> >> Hi,
> >> Can you please advise what the default latency of heartbeat keep alive
> 
> packets is?
> 
> > For Corosync or Heartbeat?
> > And I'd have thought the latency would be a function of your network
> 
> infrastructure, not the software.
> 
> >> Another question, whether the latency can be customized? If yes, how can
> 
> it be done?
> 
> >> Thanks in advance,
> >> Lev

Hi,

if you want to operate your cluster over unreliable, high-latency link s 
(internet) than perhaps you should read this:

http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ch15.html


Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140406/610f6a7f/attachment-0003.sig>