You probably already figured this out, but that setting should be on any
machines at either end of a connection across a high-latency network link.
So definitely your brokers, but also any hosts of consumers that connect to
a broker across a high-latency link.
This setting is especially important
Thank you for the reply Tim.
I think we are going with a maser/slave setup at each dc but the main hub
datacenter will have the config that notes all other data centers. Is it
recommended to do the same with the other activemq.xml configs to point back
to the hub, in case the hub goes down?
We
I'd strongly recommend setting the net.ipv4.tcp_slow_start_after_idle = 0
kernel parameter for any machine on either end of a high-latency network
link; you don't really want the congestion window closing simply because
the link isn't being used, but this is especially troublesome for
high-latency
Let me also add the systems at each datacenter are behind F5 load balancers.
Is this a good practice or should we avoid the load balancers?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Network-of-brokers-with-multiple-worldwide-data-centers-tp4693158p4693160.html
Sent
