[
https://issues.apache.org/jira/browse/FLINK-18636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
tartarus updated FLINK-18636:
-----------------------------
Description:
When flink job canceled/failed ,it need to wait all closeAsync finish.
but CompletedOperationCache’s closeAsync timeout is fixed at 300s,
so i think via configurable timeout is better.
CompletedOperationCache#closeAsync
{code:java}
@Override
public CompletableFuture<Void> closeAsync() {
return FutureUtils.orTimeout(
asyncWaitForResultsToBeAccessed(),
COMPLETED_OPERATION_RESULT_CACHE_DURATION_SECONDS,
TimeUnit.SECONDS);
}
{code}
was:
When flink job canceled/failed ,it need to wait all closeAsync finish.
but CompletedOperationCache’s closeAsync timeout is fixed at 300s,
so i think via configurable timeout is better.
> Asynchronous close via configurable timeout in seconds for
> CompletedOperationCache
> ----------------------------------------------------------------------------------
>
> Key: FLINK-18636
> URL: https://issues.apache.org/jira/browse/FLINK-18636
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Affects Versions: 1.10.0, 1.10.1, 1.11.0
> Reporter: tartarus
> Priority: Minor
>
> When flink job canceled/failed ,it need to wait all closeAsync finish.
> but CompletedOperationCache’s closeAsync timeout is fixed at 300s,
> so i think via configurable timeout is better.
> CompletedOperationCache#closeAsync
> {code:java}
> @Override
> public CompletableFuture<Void> closeAsync() {
> return FutureUtils.orTimeout(
> asyncWaitForResultsToBeAccessed(),
> COMPLETED_OPERATION_RESULT_CACHE_DURATION_SECONDS,
> TimeUnit.SECONDS);
> }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
