[
https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113591#comment-13113591
]
Roman Shaposhnik commented on HBASE-4427:
-----------------------------------------
@Jean-Daniel Cryans
> the idea of setting hbase.zookeeper.property.clientPort to a new default
> breaks about every setup I know of.
this is not correct. everything that reads hbase-default.xml will continue to
work as expected (hbase shell for example). I'm still to new to HBase to know
whether 3d party clients that are built on top of HBase APIs are forced to read
hbase-default.xml or not. Would appreciate if somebody let me know.
In general, however, I think the consensus here is pretty clear. Thanks for the
feedback and if somebody can answer the question above (on hbase-default.xml) I
think we can safely close this JIRA.
> 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
