You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "TisonKun (Jira)" <ji...@apache.org> on 2019/09/11 08:14:00 UTC
[jira] [Updated] (FLINK-14051) Deploy job cluster in attached mode
[ https://issues.apache.org/jira/browse/FLINK-14051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
TisonKun updated FLINK-14051:
-----------------------------
Description:
While working on FLINK-14048 I revisit the problem we handle deploy logic in a complicated if-else branches in {{CliFrontend#runProgram}}. Previously we said even in per-job mode and attached we deploy a session cluster for historical reasons.
However, I notice that {{#deployJobCluster}} has a parameter {{boolean detached}}. Also it is used in sql-client package. So it looks like we can deploy job cluster in attached mode as we do in sql-client package.
However, as [~xccui] answered on mailing list [here|https://lists.apache.org/x/thread.html/5464459db08f2a756af0c61eb02d34a26f04c27c62140886cad52731@%3Cuser.flink.apache.org%3E], we support only standalone session cluster for sql-client. So maybe it is not our case. Anyway, if we cannot deploy job cluster in attached mode, I'd like to know the concrete reason.
CC [~till.rohrmann] [~twalthr]
was:
While working on FLINK-14048 I revisit the problem we handle deploy logic in a complicated if-else branched in {{CliFrontend#runProgram}}. Previously we said even in per-job mode and attached we deploy a session cluster for historical reasons.
However, I notice that {{#deployJobCluster}} has a parameter {{boolean detached}}. Also it is used in sql-client package. So it looks like we can deploy job cluster in attached mode as we do in sql-client package.
However, as [~xccui] answered on mailing list [here|https://lists.apache.org/x/thread.html/5464459db08f2a756af0c61eb02d34a26f04c27c62140886cad52731@%3Cuser.flink.apache.org%3E], we support only standalone session cluster for sql-client. So maybe it is not our case. Anyway, if we cannot deploy job cluster in attached mode, I'd like to know the concrete reason.
CC [~till.rohrmann] [~twalthr]
> Deploy job cluster in attached mode
> -----------------------------------
>
> Key: FLINK-14051
> URL: https://issues.apache.org/jira/browse/FLINK-14051
> Project: Flink
> Issue Type: Sub-task
> Components: Client / Job Submission, Command Line Client
> Affects Versions: 1.10.0
> Reporter: TisonKun
> Priority: Major
> Fix For: 1.10.0
>
>
> While working on FLINK-14048 I revisit the problem we handle deploy logic in a complicated if-else branches in {{CliFrontend#runProgram}}. Previously we said even in per-job mode and attached we deploy a session cluster for historical reasons.
> However, I notice that {{#deployJobCluster}} has a parameter {{boolean detached}}. Also it is used in sql-client package. So it looks like we can deploy job cluster in attached mode as we do in sql-client package.
> However, as [~xccui] answered on mailing list [here|https://lists.apache.org/x/thread.html/5464459db08f2a756af0c61eb02d34a26f04c27c62140886cad52731@%3Cuser.flink.apache.org%3E], we support only standalone session cluster for sql-client. So maybe it is not our case. Anyway, if we cannot deploy job cluster in attached mode, I'd like to know the concrete reason.
> CC [~till.rohrmann] [~twalthr]
--
This message was sent by Atlassian Jira
(v8.3.2#803003)