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:32:10 GMT

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

ASF GitHub Bot commented on FLINK-3073:

Github user StephanEwen commented on the pull request:

    As followup to this, I would suggest two changes:
    1. Adjust the log message, to reflect that not 0.7 are either used immediately (eager
allocation) or that the managed memory is capped at 0.7 * total memory. That makes it clear
from reading the log that the memory is not pre-allocated.
    2. The web frontend should display for managed memory: (used / max). I have talked to
users who were confused, thinking despite starting the system in streaming mode, it pre-allocated
all the heap way, 

> 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

View raw message