[
https://issues.apache.org/jira/browse/ZOOKEEPER-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878631#action_12878631
]
Patrick Hunt commented on ZOOKEEPER-733:
----------------------------------------
Great, thanks for the fb Kapil. There's still one serious issue that we know
about with the patch, it's due to the way
netty handles buffering. Our old server nio code does flow control by disabling
read on the inbound sockets, but
netty aggressively buffers which means that the data's already been read by the
time we disable read. We're working
on a solution for that. Subsequently we'll have some addl work re documentation
and such. Also need to test out
encryption (ssl) support on the channels. It's in progress but I've been
distracted by other things (incl the upcoming
summit). After that we also need to add netty support on the java client side,
I'm not sure what we'll do on the c client
(to add ssl encrypt/cert support) but if you have any ideas on that we'd
appreciate the help.
> use netty to handle client connections
> --------------------------------------
>
> Key: ZOOKEEPER-733
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-733
> Project: Zookeeper
> Issue Type: Improvement
> Reporter: Benjamin Reed
> Attachments: accessive.jar, flowctl.zip, moved.zip,
> QuorumTestFailed_sessionmoved_TRACE_LOG.txt.gz, 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.
