丛鹏 created FLINK-26983:
--------------------------
Summary: When the startup mode in the command line submission task
is filled in incorrectly, the code judgment is wrong, and the error information
will be misleading
Key: FLINK-26983
URL: https://issues.apache.org/jira/browse/FLINK-26983
Project: Flink
Issue Type: Improvement
Components: Command Line Client
Affects Versions: 1.14.4, 1.12.2
Environment: idea flink1.12.2
Reporter: 丛鹏
Fix For: 1.14.4, 1.14.2
Hi, I'm using flink1.12.2 a problem is found when submitting the task of yarn
application,
An example of the Flink official website submitting a task is
./bin/flink run-application -t yarn-application ./
examples/streaming/TopSpeedWindowing. jar
If some of them are misspelled, then yarn-application is written as
yarn-appliation
One C is missing
Will report an error：
java.lang.IllegalStateException: No ClusterClientFactory found. If you were
targeting a Yarn cluster, please make sure to export the HADOOP_CLASSPATH
environment variable or have hadoop in your classpath. For more information
refer to the "Deployment" section of the official Apache Flink documentation.
BUT
I saw that the code is the 213 line configuration set encapsulated by
CliFrontend.java. There is a problem with effectiveconfiguration, resulting in
DefaultClusterClientServiceLoader.Java: 83 judgment entry error
Finally, it leads to logical judgment
if (compatibleFactories.isEmpty()) is true
then
"No ClusterClientFactory found. If you were targeting a Yarn cluster, "
+ "please make sure to export the HADOOP_CLASSPATH
environment variable or have hadoop in your "
+ "classpath. For more information refer to the
\"Deployment\" section of the official "
+ "Apache Flink documentation."
Look at all the situations that lead to the failure of the encapsulation of the
configuration class,Will prompt HADOOP_CLASSPATH environment 's reason
I think there is something wrong with the description of the error information
here, which will lead to misleading. Users mistakenly think it is their own
Hadoop_ There is a problem with the classpath environment. I hope you can reply
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
