[
https://issues.apache.org/jira/browse/FLINK-11779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173995#comment-17173995
]
Guowei Ma commented on FLINK-11779:
-----------------------------------
# What I understand is that the rest server should publish its address to the
HighAvailabilityService. The rest client should always retrieve the rest server
address from a HighAvailabilityService.
# In the default mode the -m option means two things
# User wants to use `StandaloneHaServices`
# Set the value for the `jobmanager.rpc.address`
# In the Generic CLI mode there is no -m option. It does not use the
`AbstractCustomCommandLine`. So in this mode client and server should always
respect the `HighAvailabilityServcie` in the config. I agree with [~aljoscha]
that maybe we should not expose the `jobmanager.rpc.address` to the client any
more.
> 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)
