[ 
https://issues.apache.org/jira/browse/FLINK-8576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363766#comment-16363766
 ] 

ASF GitHub Bot commented on FLINK-8576:
---------------------------------------

Github user kl0u commented on a diff in the pull request:

    https://github.com/apache/flink/pull/5420#discussion_r168137274
  
    --- Diff: 
flink-runtime/src/main/java/org/apache/flink/runtime/query/QueryableStateUtils.java
 ---
    @@ -132,9 +134,7 @@ public static KvStateServer createKvStateServer(
                                        KvStateRequestStats.class);
                        return constructor.newInstance(address, ports, 
eventLoopThreads, queryThreads, kvStateRegistry, stats);
                } catch (ClassNotFoundException e) {
    -                   final String msg = "Could not load Queryable State 
Server. " +
    -                           "Probable reason: flink-queryable-state-runtime 
is not in the classpath. " +
    -                           "Please put the corresponding jar from the opt 
to the lib folder.";
    +                   final String msg = "Could not load Queryable State 
Server. " + ERROR_MESSAGE_ON_LOAD_FAILURE;
                        if (LOG.isDebugEnabled()) {
                                LOG.debug(msg, e);
    --- End diff --
    
    The `debug` message should change as well as above, right?


> Log message for QueryableState loading failure too verbose
> ----------------------------------------------------------
>
>                 Key: FLINK-8576
>                 URL: https://issues.apache.org/jira/browse/FLINK-8576
>             Project: Flink
>          Issue Type: Improvement
>          Components: Queryable State
>    Affects Versions: 1.5.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> Whenever a job- or taskmanager is started it attempts to load the queryable 
> state via reflection. If this fails due to the classes not being in the 
> classpath (which is common and the default path) we log the full stacktrace 
> as DEBUG.
> We should reduce this to a single line as it get's really verbose when 
> sifting through debug logs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to