[
https://issues.apache.org/jira/browse/HBASE-12956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308107#comment-14308107
]
Enis Soztutar commented on HBASE-12956:
---------------------------------------
Ok, I'm gonna sink the release candidate because this is an important
regression to fix. I've reproduced this with a cluster
{{hbase.regionserver.ipc.address=0.0.0.0}}.
{code}
hbase(main):001:0> zk_dump
HBase is rooted at /hbase
Active master address: 0:0:0:0:0:0:0:0,16020,1423174431955
Backup master addresses:
Region server holding hbase:meta:
os-enis-hbase-1.0-test-feb5-1.novalocal,16020,1423173791765
Region servers:
0:0:0:0:0:0:0:0,16020,1423174437687
0:0:0:0:0:0:0:0,16020,1423174436415
0:0:0:0:0:0:0:0,16020,1423174434835
0:0:0:0:0:0:0:0,16020,1423174433653
0:0:0:0:0:0:0:0,16020,1423174438855
{code}
> 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
> 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)
