You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tajo.apache.org by "Jinho Kim (JIRA)" <ji...@apache.org> on 2014/02/12 16:08:19 UTC

[jira] [Updated] (TAJO-598) Refactoring Tajo RPC

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

Jinho Kim updated TAJO-598:
---------------------------

    Attachment: TAJO-598.patch

> Refactoring Tajo RPC
> --------------------
>
>                 Key: TAJO-598
>                 URL: https://issues.apache.org/jira/browse/TAJO-598
>             Project: Tajo
>          Issue Type: Improvement
>          Components: rpc
>    Affects Versions: 0.8-incubating
>            Reporter: Jinho Kim
>            Assignee: Jinho Kim
>         Attachments: TAJO-598.patch
>
>
> In the current implementation, all client rpc use same channel pool.
> It can cause a channel closed exception. we need both shared pool and new pool.
> In details, 
> * Fix the TajoAsyncDispatcher hang
> * Fix the Fetcher timeout
> * Fix the TaskRunner thread leak
> * Fix the client rpc reconnecting
> * Fix the unittest failure(No available resources)
> * Improve RPC thread sharing



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)