[HBASE-9961] [WINDOWS] Multicast should bind to local address

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.98.0, 0.96.1
• Component/s: Client
• Release Note: Clients now bind to multicast address configured as "hbase.status.multicast.bind.address.ip", 0.0.0.0 by default.
• Assignee: Enis Soztutar
• Reporter: Enis Soztutar
• Created: 12/Nov/13 23:16
• Updated: 16/Dec/13 18:46
• Resolved: 15/Nov/13 22:54

Description

Binding to a multicast address (such as "hbase.status.multicast.address.ip") seems to be the preferred method on most unix systems and linux(2,3). At least in RedHat, binding to multicast address might not filter out other traffic coming to the same port, but for different multi cast groups (2)]. However, on windows, you cannot bind to a non local (class D) address (1), which seems to be correct according to the spec.

1. http://msdn.microsoft.com/en-us/library/ms737550%28v=vs.85%29.aspx
2. https://bugzilla.redhat.com/show_bug.cgi?id=231899
3. http://stackoverflow.com/questions/10692956/what-does-it-mean-to-bind-a-multicast-udp-socket
4. https://issues.jboss.org/browse/JGRP-515

The solution is to bind to mcast address on linux, but a local address on windows.

TestHCM is also failing because of this.