You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
What happened
Start Dolphinscheduler in standalone mode: ./dolphinscheduler-daemon.sh start standalone-server
And then got an error: /opt/username/dolphinscheduler/apache-dolphinscheduler-dev-SNAPSHOT-bin/standalone-server/bin/start.sh: line 37: /usr/jdk64/java/bin/java: Argument list too long
What you expected to happen
It seems that the following code in dolphinscheduler-standalone-server/src/main/bin/start.sh: CP=$DOLPHINSCHEDULER_HOME/libs/standalone-server/* for d in alert-server api-server master-server worker-server; do for f in $DOLPHINSCHEDULER_HOME/../$d/libs/*.jar; do CP=$CP:$f done done
returns a very long classpath that exceeds Linux command line limit.
How to reproduce
Put dolphinscheduler executables in a folder within a deep folder hierarchy or a long name and then start the standalone server.
Search before asking
What happened
Start Dolphinscheduler in standalone mode:
./dolphinscheduler-daemon.sh start standalone-server
And then got an error:
/opt/username/dolphinscheduler/apache-dolphinscheduler-dev-SNAPSHOT-bin/standalone-server/bin/start.sh: line 37: /usr/jdk64/java/bin/java: Argument list too long
What you expected to happen
It seems that the following code in dolphinscheduler-standalone-server/src/main/bin/start.sh:
CP=$DOLPHINSCHEDULER_HOME/libs/standalone-server/* for d in alert-server api-server master-server worker-server; do for f in $DOLPHINSCHEDULER_HOME/../$d/libs/*.jar; do CP=$CP:$f done done
returns a very long classpath that exceeds Linux command line limit.
How to reproduce
Put dolphinscheduler executables in a folder within a deep folder hierarchy or a long name and then start the standalone server.
Anything else
No response
Version
dev
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: