You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias Pohl (Jira)" <ji...@apache.org> on 2023/05/04 15:32:00 UTC
[jira] [Resolved] (FLINK-31995) DirectExecutorService doesn't follow the ExecutorService contract throwing a RejectedExecutionException in case it's already shut down
[ https://issues.apache.org/jira/browse/FLINK-31995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Pohl resolved FLINK-31995.
-----------------------------------
Fix Version/s: 1.18.0
Assignee: Matthias Pohl
Resolution: Fixed
master: 8d430f51d77cf4f0d3291da6a7333f1aa9a87d22
> DirectExecutorService doesn't follow the ExecutorService contract throwing a RejectedExecutionException in case it's already shut down
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-31995
> URL: https://issues.apache.org/jira/browse/FLINK-31995
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.17.0, 1.16.1, 1.18.0
> Reporter: Matthias Pohl
> Assignee: Matthias Pohl
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.18.0
>
>
> We experienced an issue where we tested behavior using the {{DirectExecutorService}} with the {{ExecutorService}} being shutdown already. The tests succeeded. The production code failed, though, because we used a singleThreadExecutor for which the task execution failed after the executor was stopped. We should add this behavior to the {{DirectExecutorService}} as well to make the unit tests be closer to the production code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)