lincoln-lil opened a new pull request, #26779: URL: https://github.com/apache/flink/pull/26779
## What is the purpose of the change As discussed in https://lists.apache.org/thread/8gncfyy42cmj6xtyk4fqvpxwf22xk9x5, an issue that unexpected extra retries will be triggered when user async function invoke completeExceptionally in timeout. We can fix this by adding a start timestamp for future handler to help check if a retry still within configured timeout. ## Brief change log * adding a start timestamp for future handler to help check if a retry still within configured timeout. ## Verifying this change newly added test cases: * testProcessingTimeWithAlwaysTimeoutFunctionUnorderedWithRetry * testProcessingTimeWithAlwaysTimeoutFunctionOrderedWithRetry ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with @Public(Evolving): (no) - The serializers: (no ) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (no) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
