You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2011/04/12 22:42:06 UTC
[jira] [Created] (HBASE-3774) Manage ZK connections by components
and ensembles
Manage ZK connections by components and ensembles
-------------------------------------------------
Key: HBASE-3774
URL: https://issues.apache.org/jira/browse/HBASE-3774
Project: HBase
Issue Type: Improvement
Affects Versions: 0.90.2
Reporter: Jean-Daniel Cryans
Priority: Blocker
Fix For: 0.92.0
This is the real fix to HBASE-3773, we need to stop creating so many connections to ZK. Currently the problem is that we don't want to mix connections between the region server, a client, and whatever else in a JVM that requires talking to ZK. The current situation is a (non-intended) tradeoff of worse usability for easier unit testing.
Another thing to take into account is that a client or a region server needs to be able to talk to more than one ensemble at the same time (CopyTable, replication are examples).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-3774) Manage ZK connections by components
and ensembles
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029148#comment-13029148 ]
stack commented on HBASE-3774:
------------------------------
Does HBASE-3777 take care of this? I see we are careful making new HCMs and its in the HCM constructor that we go get new ZKW.
> Manage ZK connections by components and ensembles
> -------------------------------------------------
>
> Key: HBASE-3774
> URL: https://issues.apache.org/jira/browse/HBASE-3774
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.2
> Reporter: Jean-Daniel Cryans
> Priority: Blocker
> Fix For: 0.92.0
>
>
> This is the real fix to HBASE-3773, we need to stop creating so many connections to ZK. Currently the problem is that we don't want to mix connections between the region server, a client, and whatever else in a JVM that requires talking to ZK. The current situation is a (non-intended) tradeoff of worse usability for easier unit testing.
> Another thing to take into account is that a client or a region server needs to be able to talk to more than one ensemble at the same time (CopyTable, replication are examples).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HBASE-3774) Manage ZK connections by components
and ensembles
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Daniel Cryans resolved HBASE-3774.
---------------------------------------
Resolution: Duplicate
Yeah HBASE-3777 solves the same root problem.
> Manage ZK connections by components and ensembles
> -------------------------------------------------
>
> Key: HBASE-3774
> URL: https://issues.apache.org/jira/browse/HBASE-3774
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.2
> Reporter: Jean-Daniel Cryans
> Priority: Blocker
> Fix For: 0.92.0
>
>
> This is the real fix to HBASE-3773, we need to stop creating so many connections to ZK. Currently the problem is that we don't want to mix connections between the region server, a client, and whatever else in a JVM that requires talking to ZK. The current situation is a (non-intended) tradeoff of worse usability for easier unit testing.
> Another thing to take into account is that a client or a region server needs to be able to talk to more than one ensemble at the same time (CopyTable, replication are examples).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira