While reading a product documentation I came across a line in which they say product supports TCP communication in environments where multicast is not available or preferred.
Why would a company block multicast communication? or prefer TCP over it?
“Hazelcast will use multicast for discovery, it can also be configured to only use TCP/IP for environments where multicast is not available or preferred.”
Multicast introduces extra overhead for routers in the network. In order to send multicast data, each router has to store some state information about how to reach members of a multicast group. For every multicast group, routers have to maintain some state information. This is why you can’t multicast over the Internet in general, it doesn’t scale.
So scalability is one reason multicast may not be enabled. Scalability isn’t as big an issue for smaller networks, so university or corporate networks may support it. Enabling multicast requires additional configuration for routers as well, and network operators may just see no advantage in going through the extra work to maintain it if there is no need for multicast.
What the site you refer to is saying is that if multicast isn’t supported, they can use standard unicast protocols like TCP or UDP to support whatever functionality they provide.
Leave a comment
- What is the easiest way to upgrade my existing Perl 5.14 to Perl 5.16 on FreeBSD 9 using the ports system?
- Know if mysql has done its job
- Redirect https .com to https .co.uk without a valid SSL cert on .com without DNS change
- Why is it a bad idea to use customer email as from address
- 100% packets dropped on first RX queue on 3/5 raid6 iSCSI NAS devices using intel igb (resolved)