flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Shkvyra (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-5476) Fail fast if trying to submit a job to a non-existing Flink cluster
Date Mon, 24 Apr 2017 10:45:04 GMT

     [ https://issues.apache.org/jira/browse/FLINK-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmytro Shkvyra resolved FLINK-5476.
-----------------------------------
    Resolution: Resolved

> Fail fast if trying to submit a job to a non-existing Flink cluster
> -------------------------------------------------------------------
>
>                 Key: FLINK-5476
>                 URL: https://issues.apache.org/jira/browse/FLINK-5476
>             Project: Flink
>          Issue Type: Improvement
>          Components: Client
>    Affects Versions: 1.2.0, 1.3.0
>            Reporter: Till Rohrmann
>            Assignee: Dmytro Shkvyra
>            Priority: Minor
>
> In case of entering the wrong job manager address when submitting a job via {{flink run}},
the {{JobClientActor}} waits per default {{60 s}} until a {{JobClientActorConnectionException}},
indicating that the {{JobManager}} is no longer reachable, is thrown. In order to fail fast
in case of wrong connection information, we could change it such that it uses initially a
much lower timeout and only increases the timeout if it had at least once successfully connected
to a {{JobManager}} before.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message