[
https://issues.apache.org/jira/browse/FLINK-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027145#comment-14027145 ]
ASF GitHub Bot commented on FLINK-917:
--------------------------------------
GitHub user uce opened a pull request:
https://github.com/apache/incubator-flink/pull/5 [FLINK-917] Rename netty IO thread count parameters
Renames config parameters introduced in 4cd4a13415d609a2979c8fa3cf4b797c990ee8c2:
- `taskmanager.netty.numInThreads => taskmanager.io.numInThreads`, and
- `taskmanager.netty.numOutThreads => taskmanager.io.numOutThreads`.
You can merge this pull request into a Git repository by running:
$ git pull
https://github.com/uce/incubator-flink FLINK-917
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-flink/pull/5.patchTo close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5
----
commit 96dc4bb8f3bdb5a959a769f14e2d9d1262588cf5
Author: uce <
[hidden email]>
Date: 2014-06-10T22:22:11Z
[FLINK-917] Rename netty IO thread count parameters
----
> 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
> Labels: github-import
> Fix For: pre-apache
>
>
> 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)