[
https://issues.apache.org/jira/browse/FLINK-15750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-15750:
-----------------------------------
Labels: auto-unassigned pull-request-available stale-major (was:
auto-unassigned pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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)
