kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ijuma <...@git.apache.org>
Subject [GitHub] kafka pull request: KAFKA-2614; No more clients can connect after ...
Date Thu, 08 Oct 2015 15:44:48 GMT
GitHub user ijuma opened a pull request:

    https://github.com/apache/kafka/pull/288

    KAFKA-2614; No more clients can connect after `TooManyConnectionsException` threshold
(max.connections.per.ip) is reached

    * Call `ConnectionQuotas.decr` when calling `Selector.close` and when disconnections happen.
    * Expand `SocketServerTest` to test for this and to close sockets.
    * Refactor and clean-up `SocketServer` and `Acceptor` to make the code easier to understand.
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ijuma/kafka kafka-2614-connection-count-not-updated

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/288.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #288
    
----
commit 1f0786e22e23858a6e76cd40c570ffbbd91fc349
Author: Ismael Juma <ismael@juma.me.uk>
Date:   2015-10-08T15:38:24Z

    Call `ConnectionQuotas.decr` when calling `Selector.close` and when disconnections happen
    
    Also:
    * Expand `SocketServerTest` to test for this and to close sockets.
    * Refactor and clean-up `SocketServer` and `Acceptor` to make the code easier to understand.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message