[
https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113221#comment-13113221
]
Lars George commented on HBASE-4427:
------------------------------------
I agree with JD and Stack, the change will mess up those setups that only use
the defaults. I think setting it explicitly by the user on both sides is the
most sensible way. I thought about using something like an increment, or
fallbackClientPort that a cluster can use when there is an existing ZK ensemble
using the port. But then the clients would need to know where to talk to, and
might end up connecting to the wrong quorum because is uses its default ports
and there is someone now listening to it.
> It would help to run a standalone HBase's ZK on a different port
> ----------------------------------------------------------------
>
> Key: HBASE-4427
> URL: https://issues.apache.org/jira/browse/HBASE-4427
> Project: HBase
> Issue Type: Improvement
> Components: zookeeper
> Affects Versions: 0.90.4
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Priority: Minor
>
> It would be extremely helpful to have standalone HBase default to a
> non-standard port for running its embedded ZK. This would help to run HBase
> on the same host where a legitimate fully distributed ZK server, etc.
> It seems that the following addition to hbase-default.xml would be enough to
> make it happen:
> {noformat}
> + <property>
> + <name>hbase.zookeeper.property.clientPort</name>
> + <value>4181</value>
> + </property>
> {noformat}
> This will take care of the master/client for HBase and can be overridden in
> hbase-site if needed.
> Thoughts?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
