You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2014/11/11 11:54:33 UTC
[jira] [Resolved] (FLINK-1232) Allow I/O spill file writers to work
with futures/callbacks
[ https://issues.apache.org/jira/browse/FLINK-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ufuk Celebi resolved FLINK-1232.
--------------------------------
Resolution: Fixed
Fixed in c9cfe3ba9a2009c3da2cb8a39090154c30ccd88c.
(Commit has wrong issue number though... 1323 instead of 1232. I noticed it after merging. If anyone thinks we should revert the commit and add a new one with the correct issue number, just post here and I will do it.)
> Allow I/O spill file writers to work with futures/callbacks
> -----------------------------------------------------------
>
> Key: FLINK-1232
> URL: https://issues.apache.org/jira/browse/FLINK-1232
> Project: Flink
> Issue Type: Sub-task
> Components: Local Runtime
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Fix For: 0.8-incubating
>
>
> To simplify the implementation of the adaptive memory management, the asynchronous writers could use callbacks that are invoked when a memory has been successfully written.
> In the current solution, the thread writing memory segments to disk needs to keep track of how much was spilled and release that memory later.
> The callbacks can in that case release the memory directly. This is both simpler and less prone to leaks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)