[
https://issues.apache.org/jira/browse/HBASE-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935187#action_12935187
]
stack commented on HBASE-3254:
------------------------------
A patch whereby optionally servers would register themselves in zk using a
suggested hostname seems reasonable (Only tricky part is that a RegionServer
will use the 'name' the master tells it use -- see the reportForDuty code in
HRegionServer. RegionServer on startup reads its 'address' then volunteers
this to the Master but the Master could change it on the RegionServer.
Subsequently after first reportForDuty, the regionserver will always checkin
using the name the Master told it. In fact, you might be able to exploit this
behavior by patching the Master only?)
> 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.
