Return-Path: X-Original-To: apmail-flink-issues-archive@minotaur.apache.org Delivered-To: apmail-flink-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6F1F81879D for ; Thu, 3 Dec 2015 14:22:11 +0000 (UTC) Received: (qmail 31815 invoked by uid 500); 3 Dec 2015 14:22:11 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 31770 invoked by uid 500); 3 Dec 2015 14:22:11 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 31756 invoked by uid 99); 3 Dec 2015 14:22:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Dec 2015 14:22:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 128472C1F6B for ; Thu, 3 Dec 2015 14:22:11 +0000 (UTC) Date: Thu, 3 Dec 2015 14:22:11 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLINK-3073) Activate streaming mode by default MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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 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)