[
https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112983#comment-13112983
]
Roman Shaposhnik commented on HBASE-4427:
-----------------------------------------
@Jean-Daniel Cryans
> but then if you have an external client it means you have to
> change its default config in order to talk to a cluster that has a managed
> ZK,
how "external" of a client are we talking here? running on the same host or
remote?
> Something to consider would be refusing to start HBase if while starting it's
> own ZK it gets a port binding exception.
I believe that's the current behavior, which is, in fact, part of the problem
with out-of-the-box experience on nodes where there's an already running ZK
> 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
