hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-10278) Refactor to make CallQueue pluggable
Date Thu, 13 Feb 2014 22:20:20 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-10278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Li updated HADOOP-10278:
------------------------------

    Attachment: HADOOP-10278-atomicref.patch

Here's atomicref without the RWLock, using a safer drain 

The swap itself will take ~1 second to complete due to the use of poll and offer's timeouts
in the swap

It's starting to feel heavy in the Server class, so like [~ikeda]'s idea on encapsulating
this logic into a CallQueue adapter class, since it could take care of all the polling, swapping,
safeDrainTo, custom string formating for queue logging, etc

I'll see what that might look like

> 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-rwlock.patch, HADOOP-10278-atomicref.patch,
HADOOP-10278-atomicref.patch, HADOOP-10278-atomicref.patch, HADOOP-10278-atomicref.patch,
HADOOP-10278.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)

Mime
View raw message