[
https://issues.apache.org/jira/browse/FLINK-9153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473477#comment-16473477
]
ASF GitHub Bot commented on FLINK-9153:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5834
Committers usually have a lot of different responsibilities (releases,
testing, helping users on mailing lists, working on roadmap features, etc.).
All that takes a lot of time. Reviewing PRs is one important part, and we try
to do this well, but with so many users now, it is not always perfect.
One big problem is that very few committers actually take the time to look
at external contributions.
I might help to not always ping the same people (for example @zentol ,
@tillrohrmann , me, etc.) but some other committers as well. Here is a list of
other committers, it is not quite complete, some newer ones are not yet listed:
http://flink.apache.org/community.html#people
Hope that helps you understand...
> TaskManagerRunner should support rpc port range
> -----------------------------------------------
>
> Key: FLINK-9153
> URL: https://issues.apache.org/jira/browse/FLINK-9153
> Project: Flink
> Issue Type: Bug
> Components: TaskManager
> Affects Versions: 1.4.0, 1.5.0
> Reporter: vinoyang
> Assignee: vinoyang
> Priority: Major
> Fix For: 1.5.0
>
>
> TaskManagerRunner current just support one specific port :
> {code:java}
> final int rpcPort =
> configuration.getInteger(ConfigConstants.TASK_MANAGER_IPC_PORT_KEY, 0);
> {code}
> It should support port range as the document described :
> https://ci.apache.org/projects/flink/flink-docs-master/ops/config.html#taskmanager-rpc-port
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
