You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Lijie Wang (Jira)" <ji...@apache.org> on 2023/04/14 02:23:00 UTC
[jira] [Commented] (FLINK-27144) Provide timeout details when calling FutureUtils.orTimeout
[ https://issues.apache.org/jira/browse/FLINK-27144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712155#comment-17712155 ]
Lijie Wang commented on FLINK-27144:
------------------------------------
Done via master: a81ffa6d019d9891bd3a54f50fb36ad847721daa
> Provide timeout details when calling FutureUtils.orTimeout
> ----------------------------------------------------------
>
> Key: FLINK-27144
> URL: https://issues.apache.org/jira/browse/FLINK-27144
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination, Runtime / REST
> Affects Versions: 1.13.6, 1.14.4, 1.15.0, 1.16.0
> Reporter: Roman Khachatryan
> Assignee: Lijie Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.0
>
>
> There are two versions of FutureUtils.orTimeout() that use null as an error message when the timeout happens. They are used by (in 1.16):
> * DefaultScheduler.registerProducedPartitions
> * DeclarativeSlotPoolBridge.internalRequestNewSlot
> * CompletedOperationCache.closeAsync
> * TaskManagerRunner.onFatalError
> * RestClusterClient.getWebMonitorBaseUrl
> This makes it difficult to debug those timeouts, in particular during the shutdown. See [this|https://lists.apache.org/thread/5wxv2occohc6ky1g754n7o8b8ssjcqf5] thread for example.
>
> Replacing null with an actual message ease improve the debugging; the message could be made mandatory.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)