You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tajo.apache.org by "Jinho Kim (JIRA)" <ji...@apache.org> on 2013/10/14 16:25:41 UTC

[jira] [Commented] (TAJO-169) the default TAJO_WORKER_STANDBY_MODE in tajo-env.sh is wrong.

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

Jinho Kim commented on TAJO-169:
--------------------------------

+1 for the patch.
I think that should change soon the default mode

> the default TAJO_WORKER_STANDBY_MODE in tajo-env.sh is wrong.
> -------------------------------------------------------------
>
>                 Key: TAJO-169
>                 URL: https://issues.apache.org/jira/browse/TAJO-169
>             Project: Tajo
>          Issue Type: Bug
>          Components: conf and scripts
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>            Priority: Minor
>              Labels: newbie
>             Fix For: 0.2-incubating
>
>         Attachments: TAJO-169.patch
>
>
> The default tajo-env.sh contains a commented out line as follows:
> {noformat}
> # Tajo Distributed Execution Mode
> # the default mode is on-demand mode using YarnTajoResourceManager.
> # export TAJO_WORKER_STANDBY_MODE=yes
> {noformat}
> However, 'yes' should be 'true' because the script 'start-tajo.sh' determines if TAJO_WORKER_STANDBY_MODE variable is 'true' or not.



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