[
https://issues.apache.org/jira/browse/HADOOP-10278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890095#comment-13890095
]
Daryn Sharp commented on HADOOP-10278:
--------------------------------------
Given my current focus on performance, it saddens me that the get+poll would be
noticeable. Did you try tinkering with the poll time? Perhaps some number of
seconds is a reasonable time for handlers to switch over to a new queue since I
would expect that queue swapping would be an infrequent event.
Please go ahead and post the patch. It's really the combination of performance
and simplicity/maintainability that should be the determining factors.
> Refactor to make CallQueue pluggable
> ------------------------------------
>
> Key: HADOOP-10278
> URL: https://issues.apache.org/jira/browse/HADOOP-10278
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: ipc
> Reporter: Chris Li
> Attachments: HADOOP-10278.patch, subtask1.3.patch, subtask1.4.patch,
> subtask1.5.patch
>
>
> * Refactor CallQueue into an interface, base, and default implementation that
> matches today's behavior
> * Make the call queue impl configurable, keyed on port so that we minimize
> coupling
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
