[
https://issues.apache.org/jira/browse/FLINK-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-5230:
----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
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
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Safety nets against leaving dysfunctional JobManagers
> -----------------------------------------------------
>
> Key: FLINK-5230
> URL: https://issues.apache.org/jira/browse/FLINK-5230
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Stephan Ewen
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> There are certain ways that a {{JobManager}} can become dysfunctional.
> If the JobManager process continues to exist (not restarted by YARN / Mesos)
> etc, but is not doing its work properly and more, it makes the Streaming Job
> unavailable.
> There some safety nets to bring into place for that, see sub issues.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
