hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12956) Binding to 0.0.0.0 is broken after HBASE-10569
Date Thu, 05 Feb 2015 23:55:35 GMT

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

Enis Soztutar commented on HBASE-12956:
---------------------------------------

bq. Thats fine Enis Soztutar how ever without HBASE-12954 you cannot bind to an IP different
to 0.0.0.0 or the default host IP address (e.g. no way to use 127.0.0.1 in hbase.regionserver.ipc.address)
Not sure I understand it. Users might want to do the same setup as in 0.98 and 0.94, no? HBASE-12954
is not needed for a setup where the RS is multi homed, bind address is 0.0.0.0, but hostnames
are resolved via reverse DNS. 

> Binding to 0.0.0.0 is broken after HBASE-10569
> ----------------------------------------------
>
>                 Key: HBASE-12956
>                 URL: https://issues.apache.org/jira/browse/HBASE-12956
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Esteban Gutierrez
>            Assignee: Esteban Gutierrez
>            Priority: Blocker
>             Fix For: 1.0.0, 2.0.0, 1.1.0
>
>
> After the Region Server and Master code was merged, we lost the functionality to bind
to 0.0.0.0 via hbase.regionserver.ipc.address and znodes now get created with the wildcard
address which means that RSs and the master cannot connect to each other. Thanks to [~dimaspivak]
for reporting the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message