[JBoss JIRA] Closed: (NETTY-249) Suppress the sudden spike of the open file descriptor numbers on many short-living connections

[Trustin Lee (JIRA)]

     [ https://jira.jboss.org/jira/browse/NETTY-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trustin Lee closed NETTY-249.
-----------------------------

    Resolution: Done


Selector.selectNow() is called every 256 cancelled keys now.  The value 256 is hard-coded, but should work in most circumstances.

> Suppress the sudden spike of the open file descriptor numbers on many short-living connections
> ----------------------------------------------------------------------------------------------
>
>                 Key: NETTY-249
>                 URL: https://jira.jboss.org/jira/browse/NETTY-249
>             Project: Netty
>          Issue Type: Feature Request
>          Components: Transport
>            Reporter: Trustin Lee
>            Assignee: Trustin Lee
>             Fix For: 3.2.0.ALPHA1
>
>
> When a connection is closed and its selection key is cancelled, some selector provider does not release the file descriptor immediately but release it during the next Selector.select() call.  This behavior can lead to sudden spike of open file descriptor numbers, which can result in the 'too many open files' error, because the actual number of open files can be multitude of the expected number of open files.  Therefore, NioWorker and NioDatagramWorker must call Selector.selectNow() for every N cancelled keys so that the actual number of open files do not exceed (the number of the expected number of open files) + N.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira