[
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-deprioritized-major auto-deprioritized-minor auto-unassigned
(was: auto-deprioritized-major auto-unassigned 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.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned
>
> 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.20.1#820001)
