[
https://issues.apache.org/jira/browse/HADOOP-10278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898423#comment-13898423
]
Chris Li commented on HADOOP-10278:
-----------------------------------
Not sure why that is, I can re-run that test with different timeouts.
Right now I'm exploring using a ReadWriteLock to protect against that race.
As an aside, I went back to get benchmarking results for the FIFOCallQueue and
found that it has no significant difference against trunk for throughput and
client, but a 2% reduction in server cpu (p=.0055)
> 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-atomicref.patch,
> HADOOP-10278-atomicref.patch, HADOOP-10278-atomicref.patch, HADOOP-10278.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)
