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

Posted to issues@flink.apache.org by "Yangze Guo (Jira)" <ji...@apache.org> on 2022/03/17 02:03:00 UTC

[jira] [Comment Edited] (FLINK-26641) Optimize the time of fetching job status in the job submission of session cluster

    [ https://issues.apache.org/jira/browse/FLINK-26641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17507943#comment-17507943 ] 

Yangze Guo edited comment on FLINK-26641 at 3/17/22, 2:02 AM:
--------------------------------------------------------------

master: 3a80185ed5f063022523bd83e58c1b6e1e040af4
ddc97b5772a89ab7a97b4b7d0572c93704216129
9851ad03c1b9eb529625b8f52c5c936b5b48cab7


was (Author: karmagyz):
master: 3a80185ed5f063022523bd83e58c1b6e1e040af4

> Optimize the time of fetching job status in the job submission of session cluster
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-26641
>                 URL: https://issues.apache.org/jira/browse/FLINK-26641
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Client / Job Submission, Runtime / REST
>            Reporter: Yangze Guo
>            Assignee: Yangze Guo
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.16.0
>
>
> Currently, in the session cluster, the client will wait until the job initialization is finished in the job submission period. However, it will first get the job details from the `ExecutionGraphCache`. For short queries in OLAP scenarios, the job might have been finished before the cache refreshed, which increase the e2e time of fetching the result.
> We proposed to introduce a REST API for the job status to replace it.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)