[
https://issues.apache.org/jira/browse/HADOOP-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549542
]
Doug Cutting commented on HADOOP-1841:
--------------------------------------
- re-organizing imports injects noise into the patch
- any reason we can't make the listener thread also the responder, using a
single selector?
- catching OutOfMemoryError seems suspect, but i guess we already do it...
- it appears to me there are ways processResponse could exit with an exception
without error being set to true. Might it be safer to assume error=true, close
the connection in a 'finally' clause, and only set error=false for normal
returns?
- 'status' would better be named 'more'
> IPC server should write repsonses asynchronously
> ------------------------------------------------
>
> Key: HADOOP-1841
> URL: https://issues.apache.org/jira/browse/HADOOP-1841
> Project: Hadoop
> Issue Type: Improvement
> Components: ipc
> Reporter: Doug Cutting
> Assignee: dhruba borthakur
> Fix For: 0.16.0
>
> Attachments: asyncRPC-2.patch, asyncRPC-4.patch, asyncRPC-5.patch,
> asyncRPC-6.patch, asyncRPC.patch, asyncRPC.patch
>
>
> Hadoop's IPC Server currently writes responses from request handler threads
> using blocking writes. Performance and scalability might be improved if
> responses were written asynchronously.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
