Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] flink args build problem #3457

Closed
island-lonely opened this issue Aug 10, 2020 · 14 comments · Fixed by #4166
Closed

[bug] flink args build problem #3457

island-lonely opened this issue Aug 10, 2020 · 14 comments · Fixed by #4166
Assignees
Labels
bug Something isn't working
Milestone

Comments

@island-lonely
Copy link

island-lonely commented Aug 10, 2020

Describe the bug
There was a BUG in the Dolphin Scheduler-1.3.1 that Dolphin set Flink launch parameters

To Reproduce

  1. If the slot number and taskManager number are set, Jar package cannot be found when flink task is executed
  2. Among other parameters, specifying -yqu (the queue name of Flink on Yarn) or -ynm (Flink appName) is invalid

!!!! Setting other boot parameters, such as -yqu and -ynm, can cause confusion in the order in which the flink boot parameters are set
2020-08-10 21:03:31.400 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - Hadoop version: 3.0.0-cdh6.3.2
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - JVM Options:
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - -Dlog.file=/opt/flink-1.10.1/log/flink-dscheduler-client-cdh-05.log
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - -Dlog4j.configuration=file:/opt/flink-1.10.1/conf/log4j-cli.properties
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - -Dlogback.configurationFile=file:/opt/flink-1.10.1/conf/logback.xml
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - Program Arguments:
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - run
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - -m
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - yarn-cluster
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - -yjm
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - 1G
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - -ytm
2020-08-10 21:03:31.401 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - 6G
2020-08-10 21:03:31.402 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - -d
2020-08-10 21:03:31.402 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - -c
2020-08-10 21:03:31.402 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - cn.~~.analysis.DurationAndMileage
2020-08-10 21:03:31.402 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - analysis-assembly-2.3.jar
2020-08-10 21:03:31.402 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - --qu
2020-08-10 21:03:31.402 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - default
2020-08-10 21:03:31.402 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - -yqu
2020-08-10 21:03:31.402 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - test
2020-08-10 21:03:31.402 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - -ynm
2020-08-10 21:03:31.402 10.15.1.19 [main] INFO org.apache.flink.client.cli.CliFrontend - DurationAndMileage

@island-lonely island-lonely added the bug Something isn't working label Aug 10, 2020
@yangyichao-mango
Copy link
Contributor

Hi,
1.Can you successfully run in your env without using DolphinScheduler?
2.It will be better to add a screenshot to help us to locate this problem.

@1763734039
Copy link

I also encountered the same problem. If you want to specify other parameters, they will not take effect. I added them to other parameters. Then look at the worker log information, the Flink command will be spliced as follows: Flink run - M yarn Cluster - ys 2 - YJM 2 - YTM 8 - D - C com.xxx.common . task.xxx flink/xx-xxx-xx-1.0- SNAPSHOT.jar --Qu default - P 10, so the parameter will not take effect, Thank you for your reply to solve this bug

@island-lonely
Copy link
Author

Hi,
1.Can you successfully run in your env without using DolphinScheduler?
2.It will be better to add a screenshot to help us to locate this problem.

Flink can run normally in my working environment

WechatIMG444

1、when you set the first parameter in the image,Jar package cannot be found when flink task is executed

2、When setting the second parameter in the picture,parameter will not take effect

@yangyichao-mango
Copy link
Contributor

From flink params source processing code, 其他参数 will be add after the jar, so it will not take effect, @nauu please confirm the usage of 其他参数. Can we change the order of 其他参数 in front of jar?

@island-lonely
Copy link
Author

From flink params source processing code, 其他参数 will be add after the jar, so it will not take effect, @nauu please confirm the usage of 其他参数. Can we change the order of 其他参数 in front of jar?

In the first parameter of the picture
Flink 1.10
Remove the --yn/-- yarnContainer command parameter
Remove the -- yST /--yarnstreaming command parameter

@qiaozhanwei
Copy link
Contributor

qiaozhanwei commented Oct 14, 2020

flink run [OPTIONS] jar-file arguments . flink params sequence
1 . DS can set queue instead of other params set
2.
for example
flink run -m yarn-cluster -ys 1 -yn 2 -yjm 1G -ytm 2G -d -c com.journey.flink.wc.StreamWordCount flink-demo-1.0-SNAPSHOT-jar-with-dependencies.jar --qu default -yqu test -ynm testappl

other prama can follow run . but Different versions of flink version parameters are different . so add a version control or other ?

@chengshiwen
Copy link
Member

chengshiwen commented Dec 8, 2020

@islandgit In pr #4166, I have fixed this issue.

@CalvinKirs CalvinKirs linked a pull request Dec 8, 2020 that will close this issue
@Lucaszlei
Copy link
Contributor

Lucaszlei commented Jan 12, 2021

The problem was listed in the 1.3.4-release notes, and the problem was closed via 4166, but 4166 did not merge into the 1.3.4-release node.


这个问题被列在了1.3.4-release的notes中,并且这个问题通过4166被关闭,但是4166并没有合入1.3.4-release的分支呀, 这个怎么解释呢?
图片

@Lucaszlei
Copy link
Contributor

Lucaszlei commented Jan 12, 2021

The problem was listed in the 1.3.4-release notes, and the problem was closed via 4166, but 4166 did not merge into the 1.3.4-release notes.

这个问题被列在了1.3.4-release的notes中,并且这个问题通过4166被关闭,但是4166并没有合入1.3.4-release的分支呀, 这个怎么解释呢?
图片

@chengshiwen 您好,是否可以回复下此问题,有点疑惑

@chengshiwen
Copy link
Member

chengshiwen commented Jan 12, 2021

@chuyang-zl Thank you for your feedback, the pr #4166 fixed the issue #3457 has merged into dev, but not cherry-picked into the 1.3.4-release due to negligence

@CalvinKirs CalvinKirs changed the title Dolphin Scheduler 执行Flink 出现问题 [bug] flink args build problem Jan 12, 2021
@xingchun-chen xingchun-chen modified the milestones: 1.4.0, 1.3.5-release Jan 12, 2021
@Lucaszlei
Copy link
Contributor

Is there a definite release date for 1.3.5?


1.3.5-release有确定发布时间计划吗?

@dcy652701
Copy link

I am a little confused about the '--qu'. what does it means? My flink program can't deal with '--qa'. How do I get rid of this parameter?

@chengshiwen
Copy link
Member

chengshiwen commented Jan 13, 2021

@dcy652701 The option --qu is wrong, while the correct one should be -yqu which means the flink queue on yarn. Please see details in #4166
The option --qa should be invalid. If you want use custom options in flink, please set the options in other parameters based on next release 1.3.5.

@chengshiwen
Copy link
Member

@chuyang-zl It shouldn't be too long.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

10 participants