tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-275) Separating QueryMaster and TaskRunner roles in worker
Date Fri, 25 Oct 2013 02:38:01 GMT

    [ https://issues.apache.org/jira/browse/TAJO-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804949#comment-13804949

Hyunsik Choi commented on TAJO-275:

I think that it is a temporary and good way to help us develop C++ TaskRunner without QueryMaster.
This feature seems to be used by only developers rather than users. Also, In default, both
configs are true. And, the case where both are true is the same to the current mode, so it
would be compatible to users who use existing systems.

> Separating QueryMaster and TaskRunner roles in worker
> -----------------------------------------------------
>                 Key: TAJO-275
>                 URL: https://issues.apache.org/jira/browse/TAJO-275
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: Keuntae Park
>            Assignee: Keuntae Park
>         Attachments: TAJO-275.patch
> In C++ implementation of Tajo worker,
> I think it is better to maintain Java code of QueryMaster and implement only TaskRunner
as C++ code, rather than implementing both QueryMaster and TaskRunner as C++ code.
> Accordingly, standby mode worker will have following 3 modes:
> 1) TaskRunner + QueryMaster (current implementation)
> 2) TaskRunner only (C++)
> 3) QueryMaster only (java)
> And,  most workers work as C++ TaskRunner, and 1 or 2 workers work as separate QueryMasters
(java process).
> For backward compatibility, default mode should be mode 1 (TaskRunner + QueryMaster)

> To achieve the goal, it needs to separate java TaskRunner and java QueryMaster Worker
> (And then, implement C++ TaskRunner)

This message was sent by Atlassian JIRA

View raw message