You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/08/21 12:54:00 UTC

[jira] [Updated] (FLINK-16866) Make job submission non-blocking

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

ASF GitHub Bot updated FLINK-16866:
-----------------------------------
    Labels: pull-request-available  (was: )

> Make job submission non-blocking
> --------------------------------
>
>                 Key: FLINK-16866
>                 URL: https://issues.apache.org/jira/browse/FLINK-16866
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>    Affects Versions: 1.9.2, 1.10.0, 1.11.0
>            Reporter: Till Rohrmann
>            Assignee: Robert Metzger
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.12.0
>
>
> Currently, Flink waits to acknowledge a job submission until the corresponding {{JobManager}} has been created. Since its creation also involves the creation of the {{ExecutionGraph}} and potential FS operations, it can take a bit of time. If the user has configured a too low {{web.timeout}}, the submission can time out only reporting a {{TimeoutException}} to the user.
> I propose to change the notion of job submission slightly. Instead of waiting until the {{JobManager}} has been created, a job submission is complete once all job relevant files have been uploaded to the {{Dispatcher}} and the {{Dispatcher}} has been told about it. Creating the {{JobManager}} will then belong to the actual job execution. Consequently, if problems occur while creating the {{JobManager}} it will result into a job failure.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)