[
https://issues.apache.org/jira/browse/FLINK-15852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028694#comment-17028694
]
Zili Chen commented on FLINK-15852:
-----------------------------------
the stack layout is
0. YARNCLI
1. ExecutorCLI
2. DefaultCLI
so the command is handled by YARNCLI if it is found due to hadoop(yarn) in
classpath.
> Job is submitted to the wrong session cluster
> ---------------------------------------------
>
> Key: FLINK-15852
> URL: https://issues.apache.org/jira/browse/FLINK-15852
> Project: Flink
> Issue Type: Bug
> Components: Command Line Client
> Affects Versions: 1.10.0
> Reporter: Canbin Zheng
> Priority: Critical
> Fix For: 1.11.0, 1.10.1
>
>
> Steps to reproduce the problem:
> # Deploy a YARN session cluster by command {{./bin/yarn-session.sh -d}}
> # Deploy a Kubernetes session cluster by command
> {{./bin/kubernetes-session.sh -Dkubernetes.cluster-id=test ...}}
> # Try to submit a Job to the Kubernetes session cluster by command
> {{./bin/flink run -d -e kubernetes-session -Dkubernetes.cluster-id=test
> examples/streaming/WordCount.jar}}
> It's expected that the Job will be submitted to the Kubernetes session
> cluster whose cluster-id is *test*, however, the job was submitted to the
> YARN session cluster.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
