[common] Make dolphinscheduler_env.sh work when start server#9726
[common] Make dolphinscheduler_env.sh work when start server#9726zhongjiajie merged 4 commits intoapache:devfrom
Conversation
* Change dist tarball `dolphinscheduler_env.sh` location from `bin/` to `conf/`, which users could finish their change configuration operation in one single directory. and we only need to add `$DOLPHINSCHEDULER_HOME/conf` when we start our sever instead of adding both `$DOLPHINSCHEDULER_HOME/conf` and `$DOLPHINSCHEDULER_HOME/bin` * Change the `start.sh`'s path of `dolphinscheduler_env.sh` * Change the setting order of `dolphinscheduler_env.sh` * Change the related docs
Codecov Report
@@ Coverage Diff @@
## dev #9726 +/- ##
=========================================
Coverage 40.00% 40.01%
+ Complexity 4473 4472 -1
=========================================
Files 835 835
Lines 33550 33573 +23
Branches 3710 3714 +4
=========================================
+ Hits 13423 13433 +10
- Misses 18881 18889 +8
- Partials 1246 1251 +5
Continue to review full report at Codecov.
|
| DOLPHINSCHEDULER_HOME=${DOLPHINSCHEDULER_HOME:-$(cd $BIN_DIR/..; pwd)} | ||
|
|
||
| source "$BIN_DIR/dolphinscheduler_env.sh" | ||
| source "$BIN_DIR/../conf/dolphinscheduler_env.sh" |
There was a problem hiding this comment.
What about just
| source "$BIN_DIR/../conf/dolphinscheduler_env.sh" | |
| source "$DOLPHINSCHEDULER_HOME/conf/dolphinscheduler_env.sh" |
There was a problem hiding this comment.
Done and could you please take a look again? BTW, why we should add file dolphinscheduler_env.sh in all servers instead of using the file in the path bin/env/dolphinscheduler_env.sh?
There was a problem hiding this comment.
BTW, why we should add file
dolphinscheduler_env.shin all servers instead of using the file in the pathbin/env/dolphinscheduler_env.sh?
See my comment #9675 (comment) . The short answer is that bin/env/dolphinscheduler_env.sh is only available when you use install.sh to install all components in a single machine. If you install each component in a separate machine, bin/env/dolphinscheduler_env.sh is not available there, also cc @SbloodyS
|
I have a suggestion in #9675 . Because I found that many PR and issues are related to this problem. If everyone agrees, I think we can add it to this PR to avoid duplication of work. Then close other related issues. Please task a look @zhongjiajie @kezhenxu94 @caishunfeng |
`bin/env/dolphinscheduler_env.sh` will overwrite the `<server>/conf/dolphinscheduler_env.sh` when start the server using `bin/dolphinsceduler_daemon.sh` or `bin/install.sh`
|
I add feature we metiond in #9675 (comment), and after this patch merged, user s who using commad |
|
Kudos, SonarCloud Quality Gate passed! |
|
I going to merge this one |
…9726) * [common] Make dolphinscheduler_env.sh work * Change dist tarball `dolphinscheduler_env.sh` location from `bin/` to `conf/`, which users could finish their change configuration operation in one single directory. and we only need to add `$DOLPHINSCHEDULER_HOME/conf` when we start our sever instead of adding both `$DOLPHINSCHEDULER_HOME/conf` and `$DOLPHINSCHEDULER_HOME/bin` * Change the `start.sh`'s path of `dolphinscheduler_env.sh` * Change the setting order of `dolphinscheduler_env.sh` * `bin/env/dolphinscheduler_env.sh` will overwrite the `<server>/conf/dolphinscheduler_env.sh` when start the server using `bin/dolphinsceduler_daemon.sh` or `bin/install.sh` * Change the related docs








dolphinscheduler_env.shlocationfrom
bin/toconf/, which users could finish theirchange configuration operation in one single directory.
and we only need to add
$DOLPHINSCHEDULER_HOME/confwhen we start our sever instead of adding both
$DOLPHINSCHEDULER_HOME/confand$DOLPHINSCHEDULER_HOME/binstart.sh's path ofdolphinscheduler_env.shdolphinscheduler_env.shclose: #9727