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 Sat, 25 Jan 2014 02:23:40 GMT

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

Chris Li updated HADOOP-10278:

    Attachment: subtask1.patch

As per [~daryn]'s suggestions, this patch retains the original interface of the callQueue
in Server.

This patch allows the Server to use a custom implementation of BlockingQueue if the user defines

It includes one such implementation, the FIFOCallQueue, which simply imitates the LinkedBlockingQueue
(and uses the same 2-lock algorithm used in the JDK's implementation). Though it seems redundant,
the FIFOCallQueue will have greater flexibility in that it can be swapped out at runtime (coming
in a later patch).

> 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: subtask1.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

View raw message