HBase
  1. HBase
  2. HBASE-2502

HBase won't bind to designated interface when more than one network interface is available

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      See this message by Michael Segel up on the list: http://www.mail-archive.com/hbase-user@hadoop.apache.org/msg10042.html

      This comes up from time to time.

        Activity

        stack created issue -
        Ted Yu made changes -
        Field Original Value New Value
        Summary HBase won't bind to designated interface when more than one HBase won't bind to designated interface when more than one network interface is available
        Hide
        Todd Lipcon added a comment -

        Also reported here: http://getsatisfaction.com/cloudera/topics/cdh3_master_ip_address_configuration?utm_content=topic_link&utm_medium=email&utm_source=new_topic

        The way that the HBase master sets its address in ZK is to get its own hostname, look up that IP address in DNS, and publish that address.

        This doesn't work for situations where the master runs on a node with multiple IP addresses (i.e., with two NICs, one on a private subnet shared with the other nodes), unless the hostname is set to match to the desired IP address.

        We should add a bind-address setting in hbase-site.xml for the master node itself, as we can do for regionservers and for the master node info website.

        Show
        Todd Lipcon added a comment - Also reported here: http://getsatisfaction.com/cloudera/topics/cdh3_master_ip_address_configuration?utm_content=topic_link&utm_medium=email&utm_source=new_topic The way that the HBase master sets its address in ZK is to get its own hostname, look up that IP address in DNS, and publish that address. This doesn't work for situations where the master runs on a node with multiple IP addresses (i.e., with two NICs, one on a private subnet shared with the other nodes), unless the hostname is set to match to the desired IP address. We should add a bind-address setting in hbase-site.xml for the master node itself, as we can do for regionservers and for the master node info website.
        Hide
        Harsh J added a comment -

        Isn't this solved by using the hbase.master.dns.interface and hbase.master.dns.nameserver props right now?

        Show
        Harsh J added a comment - Isn't this solved by using the hbase.master.dns.interface and hbase.master.dns.nameserver props right now?
        Hide
        Joseph Beard added a comment -

        Not if you're using a hosts file for your cluster.

        Show
        Joseph Beard added a comment - Not if you're using a hosts file for your cluster.
        Hide
        Harsh J added a comment -

        Thanks for pointing out. That's true - and therefore also not the solution for the pseudo-distributed users who move across networks.

        Show
        Harsh J added a comment - Thanks for pointing out. That's true - and therefore also not the solution for the pseudo-distributed users who move across networks.
        Hide
        Robert Jäschke added a comment -

        Is there a workaround or are there any plans to fix this issue? It is really a big problem for cluster setups with several network interfaces.

        Show
        Robert Jäschke added a comment - Is there a workaround or are there any plans to fix this issue? It is really a big problem for cluster setups with several network interfaces.
        Hide
        Carter Shanklin added a comment -

        One of our users reports this is fixed by HBASE-8148. Can this issue be closed?

        Show
        Carter Shanklin added a comment - One of our users reports this is fixed by HBASE-8148 . Can this issue be closed?
        Hide
        Clay B. added a comment -

        Just to follow-up, HBASE-8148 didn't solve the ZK issue only the bind; thus why HBASE-12954 came about.

        Show
        Clay B. added a comment - Just to follow-up, HBASE-8148 didn't solve the ZK issue only the bind; thus why HBASE-12954 came about.

          People

          • Assignee:
            Unassigned
            Reporter:
            stack
          • Votes:
            5 Vote for this issue
            Watchers:
            14 Start watching this issue

            Dates

            • Created:
              Updated:

              Development