[ 
https://issues.apache.org/jira/browse/FLINK-9805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540089#comment-16540089
 ] 

Chesnay Schepler commented on FLINK-9805:
-----------------------------------------

Well that exception isn't really helpful, looks like the exceptional parsing 
path doesn't cover all cases :/ Will open a PR to fix that...

So this is indeed unexpected behavior, if you send anything to a standby JM it 
should redirect to the active one.
Is there any exception in the jobmanager logs? Usually all exceptions caused by 
REST operations are also logged on the server.

If you specify the address of the active JM I assume the submission works?



> 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)

Reply via email to