Sayat Satybaldiyev commented on FLINK-9805:

[~Zentol] But shouldn't a client and server be decoupled? If server re-directs 
a client to the different HTTP endpoint shouldn't client follow it, instead 
just crashing and do nothing?

Flink's client can be always exposed to Zookeeper address due to security 
issues to retrieve a correct leader 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

Reply via email to