[
https://issues.apache.org/jira/browse/ZOOKEEPER-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250347#comment-13250347
]
Jay Shrauner commented on ZOOKEEPER-517:
----------------------------------------
How tested:
- set file descriptor limit low on server, started server
- opened connections until no longer able to establish session
- opened additional connections to set up large pool of pending accepts
- closed connected session
- verified pending accepts made it through
For max connections per client testing, set a low value and kept opening more
than that # of connections from the same IP, verified that no longer see
sockets parked in CLOSE_WAIT.
> NIO factory fails to close connections when the number of file handles run
> out.
> -------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-517
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-517
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.4.3, 3.5.0
> Reporter: Mahadev konar
> Assignee: Jay Shrauner
> Priority: Critical
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-517.patch
>
>
> The code in NIO factory is such that if we fail to accept a connection due to
> some reasons (too many file handles maybe one of them) we do not close the
> connections that are in CLOSE_WAIT. We need to call an explicit close on
> these sockets and then close them. One of the solutions might be to move doIO
> before accpet so that we can still close connection even if we cannot accept
> connections.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
