[
https://issues.apache.org/jira/browse/FLINK-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091940#comment-15091940
]
ASF GitHub Bot commented on FLINK-3172:
---------------------------------------
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1458#issuecomment-170561792
Hmm, to me it is confusing by itself that there are different parameters
for ports in HA mode and in standalone mode.
Taking a step back, I would expect this behavior: `jobmanager.rpc.port`
should be interpreted by HA and non-HA the same way:
- If it is a single port, that port should be used.
- A `0` should pick a random port.
- A portrange should pick a port from the range.
Portranges and random ports are only cornercase useful in standalone
setups, but might be. One can start a flink cluster with a port range port, and
submit a job via the web frontend, or by explicitly specifying hostname:port in
the CLI client.
> Specify jobmanager port in HA mode
> ----------------------------------
>
> Key: FLINK-3172
> URL: https://issues.apache.org/jira/browse/FLINK-3172
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Runtime
> Affects Versions: 0.10.1
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
> Priority: Minor
>
> In HA mode, the job manager port is picked up randomly. In firewalled setups
> this can be problematic. We should add a way to use HA mode without random
> ports (like the web frontend currently does).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
