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

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2019/02/26 17:07:00 UTC

[jira] [Closed] (FLINK-5471) Properly inform JobClientActor about terminated Mesos framework

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

Till Rohrmann closed FLINK-5471.
--------------------------------
    Resolution: Won't Do

No longer a problem with Flip-6.

> Properly inform JobClientActor about terminated Mesos framework
> ---------------------------------------------------------------
>
>                 Key: FLINK-5471
>                 URL: https://issues.apache.org/jira/browse/FLINK-5471
>             Project: Flink
>          Issue Type: Improvement
>          Components: Mesos
>    Affects Versions: 1.2.0, 1.3.0
>            Reporter: Till Rohrmann
>            Priority: Minor
>
> In case that the Mesos framework running Flink terminates (e.g. exceeded number of container restarts) the {{JobClientActor}} is not properly informed. As a consequence, the client only terminates after the {{JobClientActor}} detects that it lost the connection to the JobManager ({{JobClientActorConnectionTimeoutException}}). The current default value for the timeout is 60s which is quite long to detect the connection loss in case of a termination.
> I think it would be better to notify the {{JobClientActor}} which allows it to print a better message for the user and also allows it to react quicker.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)