[
https://issues.apache.org/jira/browse/FLINK-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037830#comment-15037830
]
ASF GitHub Bot commented on FLINK-3073:
---------------------------------------
GitHub user aljoscha opened a pull request:
https://github.com/apache/flink/pull/1433
[FLINK-3073] Replace Streaming Mode by Memory Allocation Mode
Before, streaming mode (either batch or streaming) would specify how
memory is allocated on task managers.
This introduces a new configuration value taskmanager.memory.allocation
that can take values "lazy" or "eager". This controls how memory is
allocated.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aljoscha/flink stream-mode-default
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1433.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1433
----
commit bea4c112b7dbf0b7465b7419251173a742514967
Author: Aljoscha Krettek <[email protected]>
Date: 2015-12-01T15:13:55Z
[FLINK-3073] Replace Streaming Mode by Memory Allocation Mode
Before, streaming mode (either batch or streaming) would specify how
memory is allocated on task managers.
This introduces a new configuration value taskmanager.memory.allocation
that can take values "lazy" or "eager". This controls how memory is
allocated.
----
> Activate streaming mode by default
> ----------------------------------
>
> Key: FLINK-3073
> URL: https://issues.apache.org/jira/browse/FLINK-3073
> Project: Flink
> Issue Type: Improvement
> Components: TaskManager
> Reporter: Robert Metzger
> Assignee: Aljoscha Krettek
> Fix For: 1.0.0
>
>
> Currently, TaskManagers are still started in the batch mode.
> I have the impression that more users are actually using Flink for stream
> processing, and, the streaming mode also allows batch workloads.
> It would be nice to change that for the 1.0 release
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
