[
https://issues.apache.org/jira/browse/FLINK-11779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174087#comment-17174087
]
Yang Wang commented on FLINK-11779:
-----------------------------------
I second [~maguowei]'s comments. AFAIK, the {{-m host:port}}, aka
{{-Drest.address=host -Drest.port=port}}, should only take effect on standalone
non-HA mode. For other deployments, it will always be overridden in
{{YarnClusterDescriptor}} or {{KubernetesClusterDescriptor}}, which retrieves
from Yarn ApplicationReport, zookeeper or Kubernetes service.
So maybe we just need to document this behavior.
> 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)