[
https://issues.apache.org/jira/browse/FLINK-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037856#comment-15037856
]
ASF GitHub Bot commented on FLINK-3073:
---------------------------------------
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/1433#discussion_r46558633
--- Diff:
flink-runtime/src/main/scala/org/apache/flink/runtime/taskmanager/TaskManager.scala
---
@@ -1617,7 +1598,16 @@ object TaskManager {
}
}
- val preAllocateMemory: Boolean = streamingMode ==
StreamingMode.BATCH_ONLY
+ val allocationMode = configuration.getString(
+ ConfigConstants.TASK_MANAGER_MEMORY_ALLOCATION_KEY,
+ ConfigConstants.DEFAULT_TASK_MANAGER_MEMORY_ALLOCATION);
+ val preAllocateMemory: Boolean = allocationMode.equals("eager")
--- End diff --
Could we verify whether we only have "eager" or "lazy" and throw an
Exception otherwise?
> 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)
