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

["Flavio Junqueira (JIRA)" <ji...@apache.org>]

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

Flavio Junqueira commented on ZOOKEEPER-901:
--------------------------------------------

It makes sense to use netty here. @hongchao, I think you said you wanted to work on this? I'm assigning this to you based on my understanding, but feel free to drop if I got it wrong.

> 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.6.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 was sent by Atlassian JIRA
(v6.3.4#6332)