[
https://issues.apache.org/jira/browse/FLINK-9805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540008#comment-16540008
]
Chesnay Schepler commented on FLINK-9805:
-----------------------------------------
This sounds like correct behavior to me. If I explicitly specify a JM address I
would expect the client to honor that, even if it no JM exists for that address.
> HTTP Redirect to Active JM in Flink CLI
> ---------------------------------------
>
> Key: FLINK-9805
> URL: https://issues.apache.org/jira/browse/FLINK-9805
> Project: Flink
> Issue Type: Improvement
> Components: Client
> Affects Versions: 1.5.0
> Reporter: Sayat Satybaldiyev
> Assignee: vinoyang
> Priority: Minor
> Labels: newbie
>
> Flink CLI allows specifying job manager address via --jobmanager flag.
> However, in HA mode the JM can change and then standby JM does HTTP redirect
> to the active one. However, during deployment via flink CLI with --jobmanager
> flag option the CLI does not redirect to the active one. Thus fails to submit
> job with "Could not complete the operation. Number of retries has been
> exhausted"
>
> *Proposal:*
> Honor JM HTTP redirect in case leadership changes in flink CLI with
> --jobmanager flag active.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
