[
https://issues.apache.org/jira/browse/FLINK-12683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852668#comment-16852668
]
vinoyang commented on FLINK-12683:
----------------------------------
I think for logging, the good practice is that it should provide enough message
to location the problem, not through the whole log stream or the context log
information. Because not everyone has a good knowledge of all the log message's
meaning. In addition, if there are thousands of subtasks, it's hard to find the
mapping relationship and we try to collect some key issue messages from job
manager log file, we do not try to collect all the log messages. cc
[~till.rohrmann]
> Provide task manager's location information for checkpoint coordinator
> specific log messages
> --------------------------------------------------------------------------------------------
>
> Key: FLINK-12683
> URL: https://issues.apache.org/jira/browse/FLINK-12683
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Reporter: vinoyang
> Assignee: vinoyang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, the {{AcknowledgeCheckpoint}} does not contain the task manager's
> location information. When a task's snapshot task sends an ack message to the
> coordinator, we can only log this message:
> {code:java}
> Received late message for now expired checkpoint attempt 6035 from
> ccd88d08bf82245f3466c9480fb5687a of job 775ef8ff0159b071da7804925bbd362f.
> {code}
> Sometimes we need to get this sub task's location information to do the
> further debug work, e.g. stack trace dump. But, without the location
> information, It will not help to quickly locate the problem.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
