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 2018/05/24 14:54:00 UTC

[jira] [Closed] (FLINK-9416) Make job submission retriable operation in case of a ongoing leader election

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

Till Rohrmann closed FLINK-9416.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.5.1)
                       (was: 1.6.0)
                   1.5.0

Fixed via
master: 88987ebb93b4d56cc5a2efd7ef47dedab9b9d3d9
1.5.0: 44467239ab264039b37fe5e608531ae1d60cb8a1

> Make job submission retriable operation in case of a ongoing leader election
> ----------------------------------------------------------------------------
>
>                 Key: FLINK-9416
>                 URL: https://issues.apache.org/jira/browse/FLINK-9416
>             Project: Flink
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 1.5.0, 1.6.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Critical
>             Fix For: 1.5.0
>
>
> When starting a session cluster, it can happen that the job submission fails if the REST server endpoint has already gained leadership but if the leadership election for the {{Dispatcher}} is still ongoing. In such a case, we receive a error response saying that the leader election is still ongoing and fail the job submission. I think it would be nicer to also make the submission step a retriable operation in order to avoid this race condition.



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