You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2011/09/17 04:28:08 UTC
[jira] [Created] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109854#comment-13109854 ]
Roman Shaposhnik commented on HBASE-4427:
-----------------------------------------
@stack, I was hoping other members of the community would chime in (one way or the other ;-)) but I guess it is just you and me.
So here's my attempt at convincing you that this is the right thing to do: at the end of the day I believe that only an explicitly managed version of ZK can occupy a well-known client port of 2181. Every other application that uses an embedded ZK to manage some kind of an ensemble for its own purposes has to run its copy of ZK on a different port. Otherwise it is a bit like having an embedded version of Jetty that would alway bind to 8080 -- not clean and source of miscellaneous gotchas downstream when a real application server starts.
Now, perhaps, to make things extra clear we should introduce an extra property called embeddedClientPort or miniZKclientPort and let the existing be.
If you agree with this reasoning, I can attach a patch to make it happen according to the scenario I've outlined. If not -- that's also fine, but please let me know either way.
> 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113021#comment-13113021 ]
Jean-Daniel Cryans commented on HBASE-4427:
-------------------------------------------
bq. how "external" of a client are we talking here? running on the same host or remote?
Anything that doesn't use HBase's own configuration. Actually even a local client wouldn't know which port to look for since the config for whether HBase manages zk is in hbase-env.sh
bq. 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
You should use it if it's already there :)
> 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113596#comment-13113596 ]
Jean-Daniel Cryans commented on HBASE-4427:
-------------------------------------------
bq. this is not correct. everything that reads hbase-default.xml will continue to work as expected (hbase shell for example)
One example: the ZK ensemble isn't managed by HBase and the client port runs on 2181. The new hbase-default.xml now says that the default client port is 4181 so that's where the cluster and every client is going to look for.
> 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107204#comment-13107204 ]
Roman Shaposhnik commented on HBASE-4427:
-----------------------------------------
It is mostly out-of-the-box experience kind of question and you're absolutely right -- I can set it in my hbase-site.xml. However, I would like to understand a little bit better why do you think it'll be that disruptive. Suppose we change hbase-default.xml. The scenarious I see are these:
* standalone mode -- will work perfectly
* pseudo-distributed mode (hbase.cluster.distributed == true) with embedded ZK -- will work perfectly
* pseudo-distributed mode (hbase.cluster.distributed == true) with standalone ZK (hbase.zookeeper.quorum != nul) -- will work perfectly since, as far as I understand, hbase.zookeeper.quorum will override hbase.zookeeper.property.clientPort.
* fully-distributed mode with standalone ZK -- see above. Little difference between where the processes run, they will still require the same configs as far as hbase-site.xml is concerned.
Am I missing anything?
> 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113635#comment-13113635 ]
Jean-Daniel Cryans commented on HBASE-4427:
-------------------------------------------
Sorry I missed it:
bq. 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.
Yes because it's included in the HBase jar.
bq. Your concerned is answered in the comment #4 (look for embeddedClientPort or miniZKclientPort)
To which I answered:
bq. Actually even a local client wouldn't know which port to look for since the config for whether HBase manages zk is in hbase-env.sh
Lars mentioned a solution which would be to have the client trying to connect to both ports (I guess the embedded one first), but it's getting awfully complicated for everyone while just trying to resolve a corner case.
bq. Of course all of this is totally predicated on all the clients always paying attention to hbase-default.xml.
It's quite rare that you have to change the port in there, but in any case the HBase client will load any file named "hbase-site.xml" and "hbase-default.xml" if it's present on the classpath.
> 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113625#comment-13113625 ]
Roman Shaposhnik commented on HBASE-4427:
-----------------------------------------
@ Jean-Daniel Cryans
I'm sorry to drag it longer than it should be -- but you didn't answer my question. Your concerned is answered in the comment #4 (look for embeddedClientPort or miniZKclientPort). Of course all of this is totally predicated on all the clients always paying attention to hbase-default.xml. Whether they always do or not, was, in fact, my question ;-)
P.S. Sorry for not mentioning embeddedClientPort or miniZKclientPort in the description of the proposed change, I thought it would be assumed, but I should have been more explicit.
> 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113035#comment-13113035 ]
Roman Shaposhnik commented on HBASE-4427:
-----------------------------------------
@Jean-Daniel Cryans
If by local client you mean things like hbase shell -- that works quite nicely with the proposed change.
> 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107174#comment-13107174 ]
stack commented on HBASE-4427:
------------------------------
If we change this in hbase-default.xml, it will change it for all runs of hbase not just standalone. That is probably not what you want. I see over in src/test/resources/hbase-site.xml, the configuration we use for tests that we have a non-default port for zk. Is it too much trouble setting this config. in your local standalone instance Roman? Seems like a pretty disruptive change to make otherwise.
> 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107502#comment-13107502 ]
stack commented on HBASE-4427:
------------------------------
Thanks for the iteration of all cases.
You still need to convince that its better that the default port is changed for everyone for all installs rather than you change it in your hbase-site.xml because you happen to do what I'd think a rare setup where you run standalone hbase on a machine that is also hosting a zk ensemble that is running on default port.
> 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
[jira] [Commented] (HBASE-4427) It would help to run a standalone
HBase's ZK on a different port
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113050#comment-13113050 ]
Jean-Daniel Cryans commented on HBASE-4427:
-------------------------------------------
I was referring to the embeddedClientPort idea, the idea of setting hbase.zookeeper.property.clientPort to a new default breaks about every setup I know of.
> 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