Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 89B4B200D56 for ; Tue, 12 Dec 2017 17:41:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8642C160C10; Tue, 12 Dec 2017 16:41:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CB10A160BE7 for ; Tue, 12 Dec 2017 17:41:05 +0100 (CET) Received: (qmail 13976 invoked by uid 500); 12 Dec 2017 16:41:05 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 13965 invoked by uid 99); 12 Dec 2017 16:41:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2017 16:41:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 865FC1A0D2F for ; Tue, 12 Dec 2017 16:41:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id KWKtMnw1sHWI for ; Tue, 12 Dec 2017 16:41:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 690585FB3A for ; Tue, 12 Dec 2017 16:41:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 56FBCE25AB for ; Tue, 12 Dec 2017 16:41:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id C894721303 for ; Tue, 12 Dec 2017 16:41:00 +0000 (UTC) Date: Tue, 12 Dec 2017 16:41:00 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-19394) Support multi-homing env for the publication of RS status with multicast (hbase.status.published) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 12 Dec 2017 16:41:06 -0000 [ https://issues.apache.org/jira/browse/HBASE-19394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16287847#comment-16287847 ] stack commented on HBASE-19394: ------------------------------- Thanks [~brfrn169] Was thinking of removing this facility because it so little used and exotic too. You don't know how it is being used by your customer sir? Thanks. > Support multi-homing env for the publication of RS status with multicast (hbase.status.published) > -------------------------------------------------------------------------------------------------- > > 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 > Fix For: 2.0.0-beta-1 > > Attachments: 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)