[
https://issues.apache.org/jira/browse/ZOOKEEPER-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Reed updated ZOOKEEPER-733:
------------------------------------
Hadoop Flags: [Reviewed]
+1 looks good to commit. Sergey raises a valid point, but i think it should be
addressed in a separate jira given the size of this patch.
> use netty to handle client connections
> --------------------------------------
>
> Key: ZOOKEEPER-733
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-733
> Project: Zookeeper
> Issue Type: Improvement
> Components: server
> Reporter: Benjamin Reed
> Assignee: Patrick Hunt
> Fix For: 3.4.0
>
> Attachments: accessive.jar, flowctl.zip, moved.zip,
> QuorumTestFailed_sessionmoved_TRACE_LOG.txt.gz, ZOOKEEPER-733.patch,
> ZOOKEEPER-733.patch, ZOOKEEPER-733.patch, ZOOKEEPER-733.patch,
> ZOOKEEPER-733.patch, ZOOKEEPER-733.patch, ZOOKEEPER-733.patch,
> ZOOKEEPER-733.patch, ZOOKEEPER-733.patch
>
>
> we currently have our own asynchronous NIO socket engine to be able to handle
> lots of clients with a single thread. over time the engine has become more
> complicated. we would also like the engine to use multiple threads on
> machines with lots of cores. plus, we would like to be able to support things
> like SSL. if we switch to netty, we can simplify our code and get the
> previously mentioned benefits.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
