You will either have to create a custom Flink build (i.e. there's no
option to change this behavior) or disable all WARN messages by the
CliFrontend class with the logger configuration.
On 03.09.2018 15:21, Sarathy, Parth wrote:
The message is in WARN level and not in INFO or DEBUG level , so our log
analysis tool considers this as an issue. Can the CLI print this message in
INFO/DEBUG level?
-----Original Message-----
From: Chesnay Schepler [mailto:ches...@apache.org]
Sent: Monday, September 3, 2018 6:32 PM
To: Parth Sarathy <parth.sara...@microfocus.com>; user@flink.apache.org
Subject: Re: Flink 1.5.2 query
Cannot be avoided. The CLI eagerly loads client classes for yarn, which as see
fails since the hadoop classes aren't available.
If you don't use YARN you can safely ignore this.
On 03.09.2018 14:37, Parth Sarathy wrote:
Hi,
When using flink 1.5.2, “Apache Flink Only” binary
(flink-1.5.2-bin-scala_2.11), following error is seen in client log:
2018-08-30 10:56:59.129 [main] WARN
org.apache.flink.client.cli.CliFrontend
- Could not load CLI class org.apache.flink.yarn.cli.FlinkYarnSessionCli.
java.lang.NoClassDefFoundError:
org/apache/hadoop/yarn/exceptions/YarnException
at java.lang.Class.forName0(Native Method) ~[na:1.8.0_171]
at java.lang.Class.forName(Class.java:264) ~[na:1.8.0_171]
at
org.apache.flink.client.cli.CliFrontend.loadCustomCommandLine(CliFront
end.java:1208)
[flink-dist_2.11-1.5.2.jar:1.5.2]
at
org.apache.flink.client.cli.CliFrontend.loadCustomCommandLines(CliFron
tend.java:1164)
[flink-dist_2.11-1.5.2.jar:1.5.2]
at
org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:1090)
[flink-dist_2.11-1.5.2.jar:1.5.2]
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.yarn.exceptions.YarnException
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
~[na:1.8.0_171]
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
~[na:1.8.0_171]
at
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
~[na:1.8.0_171]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
~[na:1.8.0_171]
... 5 common frames omitted
There are no functional failures, but how to avoid this exception in log?
Thanks,
Parth Sarathy
--
Sent from:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
