ASF GitHub Bot commented on TAJO-2184:

GitHub user dongjinleekr opened a pull request:


    TAJO-2184: Can not run Tajo with non-default $TAJO_CONF_DIR

    start-tajo.sh was updated.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dongjinleekr/tajo feature/TAJO-2184

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1051
commit b2b21c0b3e226258d858e9c269936cebbfa59876
Author: Lee Dongjin <dong...@apache.org>
Date:   2016-10-18T12:12:41Z

    Update start-tajo.sh: add '--config' parameter when running tajo-daemon.sh


> 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