[
https://issues.apache.org/jira/browse/FLINK-14051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931388#comment-16931388
]
Till Rohrmann commented on FLINK-14051:
---------------------------------------
I think the driver mode is not what the current per-job mode offers. Instead
the driver mode is something which could be built upon the per-job mode.
I think the main problem is that in the current client implementation we
require the cluster to be deployed before we call into the user code's main
function. If the execution environment could also deploy a cluster (in case of
the per-job mode) when {{ExecutionEnvironment#execute}} is being called, then
the per-job mode could work well with multi parts jobs. It would simply deploy
for every part a dedicated per-job mode cluster.
> 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)
