You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Piotr Nowojski (Jira)" <ji...@apache.org> on 2021/06/21 07:38:00 UTC
[jira] [Closed] (FLINK-15750) Execute network flushing actions in
the mailbox instead of OutputFlusher
[ https://issues.apache.org/jira/browse/FLINK-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piotr Nowojski closed FLINK-15750.
----------------------------------
Resolution: Abandoned
> Execute network flushing actions in the mailbox instead of OutputFlusher
> ------------------------------------------------------------------------
>
> Key: FLINK-15750
> URL: https://issues.apache.org/jira/browse/FLINK-15750
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Network
> Affects Versions: 1.10.0
> Reporter: Piotr Nowojski
> Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently almost all interactions with the network stack are happening from the mailbox thread, except of {{org.apache.flink.runtime.io.network.api.writer.ResultPartitionWriter#flushAll}}, which happens from {{OutputFlusher}} thread.
> We could move {{ResultPartitionWriter#flushAll}} to happen in the mailbox thread (as a mailbox action), which would further simplify the threading model.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)