You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/04/04 06:49:00 UTC
[jira] [Updated] (FLINK-27204) FileSystemJobResultStore should operator on the ioExecutor
[ https://issues.apache.org/jira/browse/FLINK-27204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-27204:
-----------------------------------
Labels: pull-request-available (was: )
> FileSystemJobResultStore should operator on the ioExecutor
> ----------------------------------------------------------
>
> Key: FLINK-27204
> URL: https://issues.apache.org/jira/browse/FLINK-27204
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.16.0
> Reporter: Matthias Pohl
> Assignee: Wencong Liu
> Priority: Major
> Labels: pull-request-available
>
> The {{JobResultStore}} interface is synchronous currently. For the {{FileSystemJobResultStore}} this means that (possibly) IO-heavy operations have to be explicitly called moved to the ioExecutor within the Dispatcher.
> Instead, we could change the {{JobResultStore}} interface in a way that it returns {{CompletableFuture}} instances instead. That would enable us to run the {{FileSystemJobResultStore}} operations in the ioExecutor which would be set when initializing the {{{}FileSystemJobResultStore{}}}. This would move the responsibility of where to run the operation from the {{Dispatcher}} into the {{JobResultStore.}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)