[
https://issues.apache.org/jira/browse/HBASE-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719092#action_12719092
]
ryan rawson commented on HBASE-1515:
------------------------------------
To run on EC2 and similar systems we now support the same configuration as
hadoop:
<property>
<name>hbase.master.dns.interface</name>
<value>default</value>
<description>The name of the Network Interface from which a master
should report its IP address.
</description>
</property>
<property>
<name>hbase.master.dns.nameserver</name>
<value>default</value>
<description>The host name or IP address of the name server (DNS)
which a master should use to determine the host name used
for communication and display purposes.
</description>
</property>
Setting IPs on each host for config is not really practical. This is the
scalable mechanism that hadoop supports, and now we do as well!
> Address part of config option hbase.regionserver unnecessary
> ------------------------------------------------------------
>
> Key: HBASE-1515
> URL: https://issues.apache.org/jira/browse/HBASE-1515
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: Nitay Joffe
> Priority: Minor
> Fix For: 0.20.1
>
>
> We have a configuration option "hbase.regionserver" that specifies address +
> port the region servers should bind to. I believe all of our users don't
> require the address part of it and always leave it as 0.0.0.0. Most people
> rsync their configs to all the machines in the cluster, so anything other
> than 0.0.0.0 doesn't really make sense.
> We should change this option into just hbase.regionserver.port, like we have
> with the master now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
