You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2013/11/13 00:17:18 UTC
[jira] [Created] (HBASE-9961) [WINDOWS] Multicast should bind to
local address
Enis Soztutar created HBASE-9961:
------------------------------------
Summary: [WINDOWS] Multicast should bind to local address
Key: HBASE-9961
URL: https://issues.apache.org/jira/browse/HBASE-9961
Project: HBase
Issue Type: Bug
Components: Client
Reporter: Enis Soztutar
Assignee: Enis Soztutar
Fix For: 0.98.0, 0.96.1
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.
# http://msdn.microsoft.com/en-us/library/ms737550%28v=vs.85%29.aspx
# https://bugzilla.redhat.com/show_bug.cgi?id=231899
# http://stackoverflow.com/questions/10692956/what-does-it-mean-to-bind-a-multicast-udp-socket
# 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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)