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

Posted to issues@flink.apache.org by "Roman Khachatryan (Jira)" <ji...@apache.org> on 2022/04/08 12:24:00 UTC

[jira] [Created] (FLINK-27144) Provide timeout details when calling FutureUtils.orTimeout

Roman Khachatryan created FLINK-27144:
-----------------------------------------

             Summary: Provide timeout details when calling FutureUtils.orTimeout
                 Key: FLINK-27144
                 URL: https://issues.apache.org/jira/browse/FLINK-27144
             Project: Flink
          Issue Type: Improvement
    Affects Versions: 1.14.4, 1.13.6, 1.15.0, 1.16.0
            Reporter: Roman Khachatryan
             Fix For: 1.15.0, 1.16.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.1#820001)