[ 
https://issues.apache.org/jira/browse/HBASE-19394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286113#comment-16286113
 ] 

Toshihiro Suzuki commented on HBASE-19394:
------------------------------------------

Thanks [~tedyu] for reviewing the patch. I attached a new patch.

Actually, the value of the existing constant variable 
"STATUS_MULTICAST_BIND_ADDRESS" contains ".ip":
{code}
  /**
   * The address to use for binding the local socket for receiving multicast. 
Defaults to
   * 0.0.0.0.
   * @see <a 
href="https://issues.apache.org/jira/browse/HBASE-9961";>HBASE-9961</a>
   */
  public static final String STATUS_MULTICAST_BIND_ADDRESS =
      "hbase.status.multicast.bind.address.ip";
  public static final String DEFAULT_STATUS_MULTICAST_BIND_ADDRESS = "0.0.0.0";
{code}

I didn't modify it for the compatibility.

> Issue on the publication feature of RS status with multicast 
> (hbase.status.published) in multi-homeing env
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-19394
>                 URL: https://issues.apache.org/jira/browse/HBASE-19394
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, master
>            Reporter: Toshihiro Suzuki
>            Assignee: Toshihiro Suzuki
>         Attachments: HBASE-19394-v2.patch, HBASE-19394.patch
>
>
> Currently, when the publication feature is enabled 
> (hbase.status.published=true), it uses the interface which is found first:
> https://github.com/apache/hbase/blob/2e8bd0036dbdf3a99786e5531495d8d4cb51b86c/hbase-server/src/main/java/org/apache/hadoop/hbase/master/ClusterStatusPublisher.java#L268-L275
> This won't work when the host has the multiple network interfaces and the 
> unreachable one to the other nodes is selected. The interface which can be 
> used for the communication between cluster nodes should be configurable.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to