[
https://issues.apache.org/jira/browse/FLINK-11779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165650#comment-17165650
]
Aljoscha Krettek commented on FLINK-11779:
------------------------------------------
Turns out this is a smidge more complicated. Should only the {{-m}} parameter
take precedence or also a {{rest.address}} in {{flink-conf.yaml}}? Currently,
in the part of the code where we create the client HA services, we cannot
differentiate between the two cases. Plus, currently {{jobmanager.rpc.address}}
is the fallback option for {{rest.address}} so most setups would get
{{localhost}} as the {{rest.address}}.
Also, should there be a single {{rest.address} for both the server side and
client side? This is a bigger and somewhat orthogonal question, though.
> CLI ignores -m parameter if high-availability is ZOOKEEPER
> -----------------------------------------------------------
>
> Key: FLINK-11779
> URL: https://issues.apache.org/jira/browse/FLINK-11779
> Project: Flink
> Issue Type: Bug
> Components: Command Line Client
> Affects Versions: 1.7.2, 1.8.0
> Reporter: Gary Yao
> Assignee: leesf
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *Description*
> The CLI will ignores the host/port provided by the {{-m}} parameter if
> {{high-availability: ZOOKEEPER}} is configured in {{flink-conf.yaml}}
> *Expected behavior*
> * TBD: either document this behavior or give precedence to {{-m}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
