[
https://issues.apache.org/jira/browse/HBASE-11768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16805140#comment-16805140
]
stack commented on HBASE-11768:
-------------------------------
Say more [[email protected]]. I'd think you'd want IPs rather than names if k8s
but hbase (and hadoop) don't behave as far as k8s is concerned when it comes to
addresses and namings. This old issue is good on the problem
https://github.com/kubernetes/dns/issues/266 I'd be up for helping out here,
putting a more friendly k8s behavior behind a flag....
Regards the complaint you see above, the Master tells RS what name to use after
it checks in. In your case, it seems like the RS is not doing this. Paste a bit
more log around a RS connecting to cluster and I'd be up for taking a look.
Other issues making stuff work on k8s [[email protected]]?
> Register region server in zookeeper by ip address
> -------------------------------------------------
>
> Key: HBASE-11768
> URL: https://issues.apache.org/jira/browse/HBASE-11768
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 2.0.0
> Reporter: Cheney Sun
> Priority: Major
> Labels: patch
> Attachments: HBASE-11768.master.001.patch, HBASE_11768.patch
>
>
> HBase cluster isn't always setup along with a DNS server. But regionservers
> now register their hostnames in zookeeper, which bring some inconvenience
> when regionserver isn't in one DNS server. In such situation, clients have to
> maintain the ip/hostname mapping in their /etc/hosts files in order to
> resolve the hostname returned from zookeeper to the right address.
> However, this causes a lot of pain for clients to maintain the mapping,
> especially when adding new machines to the cluster, or some machines' address
> changed due to some reason. All clients need to update their host mapping
> files.
> The issue is to address this problem above, and try to add an option to let
> each regionserver record themself by ip address, instead of hostname only.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
