flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3073) Activate streaming mode by default
Date Sun, 06 Dec 2015 18:22:11 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044003#comment-15044003
] 

ASF GitHub Bot commented on FLINK-3073:
---------------------------------------

Github user rmetzger commented on the pull request:

    https://github.com/apache/flink/pull/1433#issuecomment-162334401
  
    Tested the change on a cluster with a job reading some 100GBs of data ...
    looks good ..
    
    ```
    19:07:19,537 INFO  org.apache.flink.runtime.taskmanager.TaskManager              - Using
0.7 of the currently free heap space for Flink managed heap memory (9001 MB).
    19:07:19,538 INFO  org.apache.flink.runtime.taskmanager.TaskManager              - MemoryManager
will be initialized with lazy memory allocation.
    ```


> 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)

Mime
View raw message