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

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

GitHub user zentol opened a pull request:

    https://github.com/apache/flink/pull/5420

    [FLINK-8576][QS] Reduce verbosity when classes can't be found

    This PR reduces the verbosity of DEBUG logging messages when the 
flink-queryable-state-runtime jar is not on the classpath. Instead of the full 
stacktrace we now only include the exception message.
    
    I've also modified the message to explicitly mention that this jar is only 
needed if queryable state is to be used. The previous message made it sound as 
if this was a critical issue that has to be fixed.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zentol/flink 8576

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/5420.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #5420
    
----
commit 0bdb29328324cd8c30418c99ea5e0dd66938487b
Author: zentol <chesnay@...>
Date:   2018-02-07T09:31:41Z

    [FLINK-8576][QS] Reduce verbosity when classes can't be found

----


> 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