[
https://issues.apache.org/jira/browse/FLINK-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269163#comment-14269163
]
Stephan Ewen commented on FLINK-1368:
-------------------------------------
Okay, I see that.
Does it make sense to make it configurable in the long run:
- Pure in-memory variants with "load-shedding" if the data grows too large
- Out-of-core enabled variant
> Change memory management settings for Streaming programs
> --------------------------------------------------------
>
> Key: FLINK-1368
> URL: https://issues.apache.org/jira/browse/FLINK-1368
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Affects Versions: 0.9
> Reporter: Gyula Fora
>
> Currently streaming programs use the same memory management settings as a
> batch api by reserving a large share of the heap for the runtime, while not
> making any use of it.
> This should be disabled until the streaming runtime is reworked so it makes a
> good use of this reserved space. One part where this could be most relevant
> is windowing operators where a large time window could easily cause memory
> problems with the current implementation. For windowing disk spilling should
> be implemented to increase robustness.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
