ASF GitHub Bot commented on TAJO-2184:

Github user dongjinleekr commented on the issue:

    Sure. I already checked it out. As you can see from tajo-daemon.sh and 
tajo-daemons.sh, only the first one takes --config parameter; the second one 
works as a ssh-proxy to the worker hosts. By this reason, it is sufficient to 
pass the parameter only to tajo-daemon.sh. (In detail, tajo-daemons.sh passes 
the execution command of tajo-daemon.sh to the workers via its parameters, 
including --config.)

> Can not run Tajo with non-default $TAJO_CONF_DIR
> ------------------------------------------------
>                 Key: TAJO-2184
>                 URL: https://issues.apache.org/jira/browse/TAJO-2184
>             Project: Tajo
>          Issue Type: Bug
>          Components: conf and scripts
>            Reporter: Lee Dongjin
>            Priority: Minor
> When running start-tajo with non-default TAJO_CONF_DIR, it fails to start 
> workers; More precisely, it tries to start workers with default TAJO_CONF_DIR 
> (=TAJO_HOME/conf) and fails.
> The missing of \-\-conf parameter in start-tajo.sh causes this problem. For 
> reference, I hereby attach [the similar shell code from Hadoop 
> project|https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/bin/start-all.sh]
>  - you can see '--conf' is configured here, to run workers via SSH.
> This update gives any significant improvements on performance or user 
> convenience yet, it will greatly help the users who try to update Tajo 
> version with legacy configurations or who tries debugging Tajo.

This message was sent by Atlassian JIRA

Reply via email to