You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "JIN SUN (JIRA)" <ji...@apache.org> on 2018/10/16 22:41:00 UTC

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

JIN SUN created FLINK-10576:
-------------------------------

             Summary: Introduce Machine/Node/TM health management
                 Key: FLINK-10576
                 URL: https://issues.apache.org/jira/browse/FLINK-10576
             Project: Flink
          Issue Type: Improvement
          Components: ResourceManager
            Reporter: JIN SUN
            Assignee: JIN SUN
             Fix For: 1.8.0


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
(v7.6.3#76005)