[
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-deprioritized-major auto-deprioritized-minor auto-unassigned
pull-request-available (was: auto-deprioritized-major auto-unassigned
pull-request-available stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned, pull-request-available
> 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.20.1#820001)
