Hi all,
In unit tests that use the LocalFilinkMiniCluster, with Flink 1.4, I now get this warning in my logs: > 18/01/31 13:28:19 WARN query.QueryableStateUtils:76 - Could not load Queryable State Client Proxy. Probable reason: flink-queryable-state-runtime is not in the classpath. Please put the corresponding jar from the opt to the lib folder. > 18/01/31 13:28:19 DEBUG query.QueryableStateUtils:79 - Caught exception > java.lang.ClassNotFoundException: org.apache.flink.queryablestate.client.proxy.KvStateClientProxyImpl > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:335) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at org.apache.flink.runtime.query.QueryableStateUtils.createKvStateClientProxy(QueryableStateUtils.java:67) > at org.apache.flink.runtime.taskexecutor.TaskManagerServices.createNetworkEnvironment(TaskManagerServices.java:339) > at org.apache.flink.runtime.taskexecutor.TaskManagerServices.fromConfiguration(TaskManagerServices.java:159) > at org.apache.flink.runtime.minicluster.LocalFlinkMiniCluster.startTaskManager(LocalFlinkMiniCluster.scala:240) From what I see in the code, this warning will always be triggered, yes? It seems odd, if I’m not explicitly setting up to use queryable state, that this is flagged as a problem. Is there any way in test code to explicitly configure things to avoid it? Thanks, — Ken -------------------------------------------- http://about.me/kkrugler +1 530-210-6378 |
Hmm, this seems indeed strange. Thanks for reporting the issue Ken. @Kostas: Do you know what is happening here? Can it be avoided or should we file a JIRA for this? 2018-01-31 23:13 GMT+01:00 Ken Krugler <[hidden email]>: Hi all, |
This is expected behavior; we try to
load the queryable state classes via reflection as it is an
optional feature.
I'll open a jira to make it less verbose if the classes cannot be found, in which case the stacktrace isn't particularly interesting anyway. On 05.02.2018 10:18, Fabian Hueske wrote:
|
Free forum by Nabble | Edit this page |