[
https://issues.apache.org/jira/browse/FLINK-10162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xymaqingxiang updated FLINK-10162:
----------------------------------
Description:
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!
was:
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:
> Add host in checkpoint detail
> -----------------------------
>
> Key: FLINK-10162
> URL: https://issues.apache.org/jira/browse/FLINK-10162
> Project: Flink
> Issue Type: Improvement
> Reporter: xymaqingxiang
> Assignee: xymaqingxiang
> Priority: 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
>
>
> 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
(v7.6.3#76005)
