tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keuntae Park (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAJO-274) Maintaining connectivity to Tajo master even though the restart of the Tajo master
Date Fri, 25 Oct 2013 00:54:01 GMT

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

Keuntae Park updated TAJO-274:
------------------------------

    Attachment: TAJO-274.patch

I've uploaded the patch for the issue

- It adds Singleton based connection management (RpcConnectionPool)
   This is not a traditional connection pool but managing a connection object because one
NettyClientBase object can already handle multiple calls concurrently and also it is rare
that one server has multiple connection at the same time.

- Connection retry is added in TajoClient, Heartbeat request from Worker to TajoMaster, and
CatalogClient.

- This patch also resolves the following issues:
  TAJO-153
  TAJO-138


> Maintaining connectivity to Tajo master even though the restart of the Tajo master
> ----------------------------------------------------------------------------------
>
>                 Key: TAJO-274
>                 URL: https://issues.apache.org/jira/browse/TAJO-274
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: Keuntae Park
>         Attachments: TAJO-274.patch
>
>
> Currently, when you restart the Tajo master, you should restart all the workers and clients
also.
> When client or worker has problem with connection to Tajo master due to the master restart,
it needs to close the previous connection and try to reconnect to the master



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message