You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/02/29 14:19:19 UTC
[jira] [Commented] (FLINK-3535) Decrease logging verbosity of
StackTraceSampleCoordinator
[ https://issues.apache.org/jira/browse/FLINK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171854#comment-15171854 ]
ASF GitHub Bot commented on FLINK-3535:
---------------------------------------
GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/1732
[FLINK-3535] [runtime-web] Decrease log verbosity of StackTraceSampleCoordinator
@rmetzger pointed out during release testing that logging in `StackTraceSampleCoordinator` can be quite verbose. I think that it is a valid point. If something is wrong with the stack trace sampling, the user can still investigate the issue in `DEBUG` log level.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/flink 3535-log_stacks
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1732.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 #1732
----
commit 0242387500fc745896abff2c70fb9b1927dc74f9
Author: Ufuk Celebi <uc...@apache.org>
Date: 2016-02-29T13:14:35Z
[FLINK-3535] [runtime-web] Decrease log verbosity of StackTraceSampleCoordinator
----
> Decrease logging verbosity of StackTraceSampleCoordinator
> ---------------------------------------------------------
>
> Key: FLINK-3535
> URL: https://issues.apache.org/jira/browse/FLINK-3535
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
> Priority: Minor
>
> Logging in StackTraceSampleCoordinator is verbose and can possible confuse users, for example if a task manager dies, you see time out messages. Let's log these on DEBUG level as they are only relevant if something fishy is going on and the user has an interest in understanding what the issue is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)