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 2023/09/11 05:14:00 UTC

[jira] [Commented] (FLINK-33054) Align the job execution result fetching timeout in CollectResultFetcher with akka timeout

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

Yangze Guo commented on FLINK-33054:
------------------------------------

master: 9c91ea3d35528ddc6a5d5be08407d5b0c71f2e76

> Align the job execution result fetching timeout in CollectResultFetcher with akka timeout
> -----------------------------------------------------------------------------------------
>
>                 Key: FLINK-33054
>                 URL: https://issues.apache.org/jira/browse/FLINK-33054
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Gateway
>    Affects Versions: 1.18.0
>            Reporter: Yangze Guo
>            Assignee: Yangze Guo
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.19.0
>
>
> Currently in CollectResultFetcher, the job execution result will be fetched after job's termination. In FLINK-17735, we arbitrarily introduce a static timeout for this rpc call. However, in OLAP scenario, the Dispatcher endpoint might be too busy to reply in time. We'd like to set it according to the akka ask timeout, which is commonly used as rpc timeout in Flink.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)