[
https://issues.apache.org/jira/browse/ZOOKEEPER-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889909#action_12889909
]
Patrick Hunt commented on ZOOKEEPER-733:
----------------------------------------
while testing I did notice a problem - closed client connections are staying in
"time_wait" state for a long period of time.
this test was done by starting the server, then connecting a java NIO based
client using the shell, then quitting the shell using "quit". Is this the shell
or Netty?
In netty factory we are setting the linger time to 2 sec, however this doesn't
seem to be used? According to netstat the socket is held in time_wait for much
longer than 2 sec.
> 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
>
>
> 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.
