[
https://issues.apache.org/jira/browse/FLINK-33054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yangze Guo updated FLINK-33054:
-------------------------------
Summary: Align the job execution result fetching timeout in
CollectResultFetcher with akka timeout (was: Align the job execution result
fetching timeout in CollectResultFetcher to akka timeout)
> 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
> 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)
