[
https://issues.apache.org/jira/browse/FLINK-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328667#comment-17328667
]
Flink Jira Bot commented on FLINK-8541:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Mesos RM should recover from failover timeout
> ---------------------------------------------
>
> Key: FLINK-8541
> URL: https://issues.apache.org/jira/browse/FLINK-8541
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Mesos, Runtime / Coordination
> Affects Versions: 1.3.0
> Reporter: Eron Wright
> Priority: Major
> Labels: stale-major
>
> When a framework disconnects unexpectedly from Mesos, the framework's Mesos
> tasks continue to run for a configurable period of time known as the failover
> timeout. If the framework reconnects to Mesos after the timeout has
> expired, Mesos rejects the connection attempt. It is expected that the
> framework discard the previous framework ID and then connect as a new
> framework.
> When Flink is in this situation, the only recourse is to manually delete the
> ZK state where the framework ID kept. Let's improve the logic of the Mesos
> RM to automate that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
