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 2020/01/24 11:09:00 UTC

[jira] [Updated] (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 updated FLINK-15750:
-----------------------------------
    Summary: Execute network flushing actions in the mailbox instead of OutputFlusher  (was: Execute network flushing actions in the mailbox)

> 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
>            Assignee: Piotr Nowojski
>            Priority: Major
>
> 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)