Hi Madhav,
Can you set the log level to DEBUG in the log4j-client configuration file?
Then post the log. I can try to locate it through the log.
Thanks, vino.
makelkar 于2018年8月17日周五 上午1:27写道：
> Hi Vino,
>We should not have to specify class name using -c option to run
> job in
Hi Vino,
We should not have to specify class name using -c option to run
job in detached mode. I tried that this morning but it also didn't work.
flink CLI always starts in interactive mode, and somehow ignores
option -yd specified in yarn-cluster mode. Can someone verify
Hi Marvin777,
You are wrong. It uses the Flink on YARN single job mode and should use the
"-yd" parameter.
Hi Madhav,
I seem to have found the problem, the source code of your log is here.[1]
It is based on a judgment method "isUsingInteractiveMode".
The source code for this method is
Hi, Madhav,
> ./flink-1.4.2/bin/flink run -m yarn-cluster *-yd* -yn 2 -yqu "default"
> -ytm 2048 myjar.jar
Modified to, ./flink-1.4.2/bin/flink run -m yarn-cluster -*d* -yn 2 -yqu
"default" -ytm 2048 myjar.jar
[image: image.png]
madhav Kelkar 于2018年8月16日周四 上午5:01写道：
> Hi there,
>
>
Hi there,
I am trying to run a single flink job on YARN in detached mode. as per
the docs for flink 1.4.2, I am using -yd to do that.
The problem I am having is the flink bash script doesn't terminate
execution and return until I press control + c. In detached mode, I would
expect the flink
