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

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-10576:
-----------------------------------
    Labels: auto-unassigned stale-major  (was: auto-unassigned)

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.


> 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
>            Priority: Major
>              Labels: auto-unassigned, stale-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)