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 Wed, 23 Oct 2013 05:12:44 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

I've uploaded the patch for the issue.

- Worker mode added in configuration
  tajo.worker.mode.querymaster (default: true)
  tajo.worker.mode.taskrunner (default: true)
- Following shell command is added
  (in bin/start-tajo.sh)
    "$bin/tajo-daemons.sh" --host querymasters cd "$TAJO_HOME" \; "$bin/tajo-daemon.sh" start
  (in bin/stop-tajo.sh)
    "$bin/tajo-daemons.sh" --host querymasters cd "$TAJO_HOME" \; "$bin/tajo-daemon.sh" stop
- If not specified in configuration, worker works as before, 
  i.e., one worker has both querymaster and taskrunner roles.
- How to have querymaster and taskrunner as separate daemons:
   1) add following in conf/tajo-site.xml
   2) add list of querymaster servers in conf/querymaster
   3) execute bin/tajo-start.sh 
- How to start/stop querymaster in a given server
   bin/tajo-daemon.sh start querymaster
   bin/tajo-daemon.sh stop querymaster

> 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)
> As a result,  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)

This message was sent by Atlassian JIRA

View raw message