You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2020/11/20 12:12:00 UTC

[jira] [Commented] (FLINK-10576) Introduce Machine/Node/TM health management

    [ https://issues.apache.org/jira/browse/FLINK-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236105#comment-17236105 ] 

Robert Metzger commented on FLINK-10576:
----------------------------------------

I would suggest closing this ticket as a duplicate of FLINK-5621.
If there are no objections, I'll close it soon.

> Introduce Machine/Node/TM health management
> -------------------------------------------
>
>                 Key: FLINK-10576
>                 URL: https://issues.apache.org/jira/browse/FLINK-10576
>             Project: Flink
>          Issue Type: New Feature
>          Components: Runtime / Coordination
>            Reporter: JIN SUN
>            Assignee: ryantaocer
>            Priority: Major
>
> When a task failed we can identify whether it was due to environment issues, especially when multiple tasks report environment error from some TM/Machine/Node, there are high possibility that this TM has issue, and if we found multiple tasks became slow in some certain node, we should put the machine into probation. 
>  * we should avoid schedule new task to it
>  * release the task manager when all tasks are drained and allocated new one if needed



--
This message was sent by Atlassian Jira
(v8.3.4#803005)