You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nico Kruber (JIRA)" <ji...@apache.org> on 2018/09/10 09:24:00 UTC
[jira] [Resolved] (FLINK-10131) Improve logging around
ResultSubpartition
[ https://issues.apache.org/jira/browse/FLINK-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nico Kruber resolved FLINK-10131.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.5.4
1.7.0
1.6.1
Fixed via:
- master: 5f8d91faeb9b2ab8feb919c717935065b473546c
- release-1.6: de0b3e125a7ea5c32382e428ba059addbc23bb0a
- release-1.5: 928f2d1fd8964c7855149622f6c052a8e2776ee0
> Improve logging around ResultSubpartition
> -----------------------------------------
>
> Key: FLINK-10131
> URL: https://issues.apache.org/jira/browse/FLINK-10131
> Project: Flink
> Issue Type: Improvement
> Components: Logging, Network
> Affects Versions: 1.5.2, 1.6.0, 1.7.0
> Reporter: Nico Kruber
> Assignee: Nico Kruber
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.1, 1.7.0, 1.5.4
>
>
> All log messages in {{PipelinedSubpartition}} and {{SpillableSubpartition}} should contain the task name to improve debugging based on log files. Furthermore, subpartition log messages should at least contain their subpartition index to make them distinguishable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)