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-275) Separating QueryMaster and TaskRunner roles in worker
Date Fri, 25 Oct 2013 04:24:34 GMT

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

Keuntae Park updated TAJO-275:

    Attachment: TAJO-275.patch_2

Thank you for the review, Jihoon

I've uploaded another patch:
- when both tajo.worker.mode.querymaster, tajo.worker.mode.taskrunner are set as false, worker
is terminated with fatal message.
(if parameter is not set, it is treated as true)
- and, rebase

> 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, TAJO-275.patch_2
> 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