flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chesnay Schepler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-9805) HTTP Redirect to Active JM in Flink CLI
Date Thu, 12 Jul 2018 12:58:00 GMT

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

Chesnay Schepler commented on FLINK-9805:

No, the PR references the correct JIRA. The PR is related to this issue since it fixes the
error message that is printed under the circumstances the user described.

> 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, pull-request-available
> 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

This message was sent by Atlassian JIRA

View raw message