[
https://issues.apache.org/jira/browse/FLINK-10162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10162:
-----------------------------------
Labels: auto-unassigned pull-request-available stale-major (was:
auto-unassigned pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Add host in checkpoint detail
> -----------------------------
>
> Key: FLINK-10162
> URL: https://issues.apache.org/jira/browse/FLINK-10162
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Reporter: xymaqingxiang
> Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-major
> Attachments: image-2018-08-16-21-14-57-221.png,
> image-2018-08-16-21-15-42-167.png, image-2018-08-16-21-15-46-585.png,
> image-2018-08-16-21-36-04-977.png
>
>
> When a streaming job run for a long time, there will be failures at
> checkpoint. We will have a requirement to look at the log for the
> corresponding task and the performance of the machine on which the task is
> located.
> Therefore, I suggest that add the host information to the checkpoint so that
> if the checkpoint fails, you can specifically login to the appropriate
> machine to see the cause of the failure.
> The failures are as follows:
> !image-2018-08-16-21-14-57-221.png!
> !image-2018-08-16-21-15-46-585.png!
> The revised representation is as follows:
> !image-2018-08-16-21-36-04-977.png!
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
