[
https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112977#comment-13112977
]
Jean-Daniel Cryans commented on HBASE-4427:
-------------------------------------------
For a moment I liked the embeddedClientPort idea, 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, and that port wouldn't be easy to find.
There's also the problem of those already running that kind of setup that all
of a sudden would need to change their configs.
I'm -1.
Something to consider would be refusing to start HBase if while starting it's
own ZK it gets a port binding exception. I'm not sure what the current behavior
is.
> 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
