You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2014/06/13 16:40:01 UTC
[jira] [Resolved] (FLINK-917) Rename netty IO Thread count
parameters
[ https://issues.apache.org/jira/browse/FLINK-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-917.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: pre-apache)
0.6-incubating
Assignee: Ufuk Celebi
Fixed in commit c81d7b02e0affb875af2851fc7c611a1976d69a1
> Rename netty IO Thread count parameters
> ---------------------------------------
>
> Key: FLINK-917
> URL: https://issues.apache.org/jira/browse/FLINK-917
> Project: Flink
> Issue Type: Bug
> Reporter: GitHub Import
> Assignee: Ufuk Celebi
> Labels: github-import
> Fix For: 0.6-incubating
>
>
> How about we rename the config parameters for `taskmanager.netty.numOutThreads` and `taskmanager.netty.numInThreads`? That way we make it "independent" of the underlying implementation. The same parameter should also configure the number of I/O threads if we should choose to go with zeroMQ for streaming, or so...
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/stratosphere/stratosphere/issues/917
> Created by: [StephanEwen|https://github.com/StephanEwen]
> Labels:
> Created at: Sun Jun 08 16:12:44 CEST 2014
> State: open
--
This message was sent by Atlassian JIRA
(v6.2#6252)