[
https://issues.apache.org/jira/browse/HBASE-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935102#action_12935102
]
Eric Tschetter commented on HBASE-3254:
---------------------------------------
Not yet. I worked around it by mucking with my hosts file and setting up an
SSH-based SOCKS proxy for now. If I get some time, I'll take a stab at a
patch.
I think that it should be reasonable to just have a System/hbase conf
property that the HRegionServer and HMaster look at to get the address that
they publish. If that is not set, then just do what it does now.
https://issues.apache.org/jira/browse/HBASE-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935040#action_12935040]
should be using hostnames rather than IPs I'd say)?
EC2 to connect to the cluster. But, each of the nodes appears to be
publishing its IP address into zookeeper. The problem is that the nodes on
EC2 see a 10. IP address that is only resolvable inside of EC2.
externally and internally, so it would be nice if I could tell each of the
processes what host to publish into zookeeper via a property. As it stands,
I have to do ssh tunnelling/muck with the hosts file in order to get my
client to connect.
public vs. private access. That might only ever happen on EC2, but it might
happen elsewhere. I don't really know :).
> Ability to specify the "host" published in zookeeper
> ----------------------------------------------------
>
> Key: HBASE-3254
> URL: https://issues.apache.org/jira/browse/HBASE-3254
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.89.20100924
> Reporter: Eric Tschetter
>
> We are running HBase on EC2 and I'm trying to get a client external from EC2
> to connect to the cluster. But, each of the nodes appears to be publishing
> its IP address into zookeeper. The problem is that the nodes on EC2 see a
> 10. IP address that is only resolvable inside of EC2.
> Specifically for EC2, there is a DNS name that will resolve properly both
> externally and internally, so it would be nice if I could tell each of the
> processes what host to publish into zookeeper via a property. As it stands,
> I have to do ssh tunnelling/muck with the hosts file in order to get my
> client to connect.
>
> This problem could occur anywhere that you have a different DNS entry for
> public vs. private access. That might only ever happen on EC2, but it might
> happen elsewhere. I don't really know :).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
