You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2010/10/18 01:21:26 UTC

[jira] Commented: (ZOOKEEPER-901) Redesign of QuorumCnxManager

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921921#action_12921921 ] 

Patrick Hunt commented on ZOOKEEPER-901:
----------------------------------------

Thoughts regarding netty support? We've been adding netty support to the client<->server connection mechanisms. My intent was to eventually modify the server<->server connections (quorum/election) similarly. You might want to consider this when refactoring -- either adding directly or just making sure it will be easy(ier) to add netty eventually.

> Redesign of QuorumCnxManager
> ----------------------------
>
>                 Key: ZOOKEEPER-901
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-901
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: leaderElection
>    Affects Versions: 3.3.1
>            Reporter: Flavio Junqueira
>            Assignee: Flavio Junqueira
>             Fix For: 3.4.0
>
>
> QuorumCnxManager manages TCP connections between ZooKeeper servers for leader election in replicated mode. We have identified over time a couple of deficiencies that we would like to fix. Unfortunately, fixing these issues requires a little more than just generating a couple of small patches. More specifically, I propose, based on previous discussions with the community, that we reimplement QuorumCnxManager so that we achieve the following:
> # Establishing connections should not be a blocking operation, and perhaps even more important, it shouldn't prevent the establishment of connections with other servers;
> # Using a pair of threads per connection is a little messy, and we have seen issues over time due to the creation and destruction of such threads. A more reasonable approach is to have a single thread and a selector.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.