Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Wed, 3 May 2017 10:19:04 +0000 (UTC)
From: "Chesnay Schepler (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.13001780.1472669140000.113772.1493806744221@Atlassian.JIRA>
In-Reply-To: <JIRA.13001780.1472669140000@Atlassian.JIRA>
References: <JIRA.13001780.1472669140000@Atlassian.JIRA> <JIRA.13001780.1472669140633@jira-lw-us.apache.org>
Subject: [jira] [Assigned] (FLINK-4545) Flink automatically manages TM
 network buffer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 03 May 2017 10:19:07 -0000


     [ https://issues.apache.org/jira/browse/FLINK-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler reassigned FLINK-4545:
---------------------------------------

    Assignee: Nico Kruber

> Flink automatically manages TM network buffer
> ---------------------------------------------
>
>                 Key: FLINK-4545
>                 URL: https://issues.apache.org/jira/browse/FLINK-4545
>             Project: Flink
>          Issue Type: Wish
>          Components: Network
>            Reporter: Zhenzhong Xu
>            Assignee: Nico Kruber
>            Priority: Blocker
>             Fix For: 1.3.0
>
>
> Currently, the number of network buffer per task manager is preconfigured and the memory is pre-allocated through taskmanager.network.numberOfBuffers config. In a Job DAG with shuffle phase, this number can go up very high depends on the TM cluster size. The formula for calculating the buffer count is documented here (https://ci.apache.org/projects/flink/flink-docs-master/setup/config.html#configuring-the-network-buffers).  
> #slots-per-TM^2 * #TMs * 4
> In a standalone deployment, we may need to control the task manager cluster size dynamically and then leverage the up-coming Flink feature to support scaling job parallelism/rescaling at runtime. 
> If the buffer count config is static at runtime and cannot be changed without restarting task manager process, this may add latency and complexity for scaling process. I am wondering if there is already any discussion around whether the network buffer should be automatically managed by Flink or at least expose some API to allow it to be reconfigured. Let me know if there is any existing JIRA that I should follow.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)