GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/1172
KAFKA-3489; Update request metrics if a client closes a connection while
the broker response is in flight
I also fixed a few issues in `SocketServerTest` and included a few
clean-ups.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijuma/kafka
kafka-3489-update-request-metrics-if-client-closes
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1172.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 #1172
----
commit 896a0ff83060a06c08835f32d0734baa6a61a98a
Author: Ismael Juma <ism...@juma.me.uk>
Date: 2016-04-01T00:52:47Z
Close client sockets on `tearDown`
commit f62f9e008cde85325265c53fb3db75eda1cc0cad
Author: Ismael Juma <ism...@juma.me.uk>
Date: 2016-04-01T00:54:04Z
Fix `testMaxConnectionsPerIpOverrides` to do what it's supposed to do
commit 23c4acc664bf0e6610917af5cfae1f10cfe3a7d6
Author: Ismael Juma <ism...@juma.me.uk>
Date: 2016-04-01T11:26:34Z
Update request metrics if a client closes a connection while the broker
response is in flight
commit d94b9b3e853a3ae2528eafbe56b9b54e03551dec
Author: Ismael Juma <ism...@juma.me.uk>
Date: 2016-04-01T11:28:41Z
Minor clean-ups in `Selector` and `RequestChannel`
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
