[
https://issues.apache.org/jira/browse/DRILL-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pritesh Maker updated DRILL-6266:
---------------------------------
Fix Version/s: (was: 1.14.0)
> Incorrect log path when Drill launched with --site option
> ---------------------------------------------------------
>
> Key: DRILL-6266
> URL: https://issues.apache.org/jira/browse/DRILL-6266
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.13.0
> Reporter: Paul Rogers
> Priority: Minor
>
> Drill supports the --site option to specify where user-specific files reside.
> These include config files, jars, system libraries and so on. One of the
> purposes of the site directory is to allow the same Drill install to work
> with multiple different configurations.
> Part of that functionality is to locate the log directory in the site
> directory so that each configuration can have its own file. This appears to
> not be working, at least for DoY.
> Install Drill 1.13. Set up Drill-on-YARN as described in
> [USAGE.md|https://github.com/apache/drill/blob/master/drill-yarn/USAGE.md].
> Before launching DoY, use the debug option to display the environment in
> which the DoY client runs.
> {noformat}
> $DRILL_HOME/bin/drill-on-yarn.sh --site $DRILL_SITE debug
> {noformat}
> Observe the following:
> {noformat}
> DRILL_SITE=/Users/yourname/site
> DRILL_LOG_PREFIX=/Users/yourname/apache-drill-1.13.0/log/drillbit
> {noformat}
> Expected:
> {noformat}
> DRILL_LOG_PREFIX=/Users/yourname/site/log
> {noformat}
> There exists a Drill-on-YARN unit test to verify this behavior. But, that
> test has had problems due to Drill's use of common, global directories. We
> should disable that feature (there is a separate JIRA for that) so we can run
> the tests, which should have caught this bug. (If the tests don't catch this
> bug, they should be extended so that they do.)
> The result is that, under Drill 1.13, users cannot run multiple Drill servers
> from a single install. This is not a huge issue for most users, but it does
> block certain obscure use cases that we had intended to support.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
