[
https://issues.apache.org/jira/browse/FLINK-38118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007954#comment-18007954
]
shilei-ly commented on FLINK-38118:
-----------------------------------
I think we can do this through flink client heartbeat. [~xtsong] [~fcsaky]
[~gaborgsomogyi] Can you give me some suggestions? I want to submit a PR to
fix this bug.
> The execution.attached=true parameter does not take effect in application mode
> ------------------------------------------------------------------------------
>
> Key: FLINK-38118
> URL: https://issues.apache.org/jira/browse/FLINK-38118
> Project: Flink
> Issue Type: Bug
> Components: Client / Job Submission
> Affects Versions: 2.0.0, 1.20.2
> Reporter: shilei-ly
> Priority: Major
>
> In FLINK-35625, flink merged the per-job mode and application mode.
> Currently, flink1.20 and flink2.x only support application mode, but in
> application mode, the *execution.attached=true* and
> *execution.shutdown-on-attached-exit=true* parameter has no effect. I think
> application mode should support these parameters, because attach mode is very
> useful in some scenarios, such as using attach mode in dolphinscheduler
> scheduler to monitor flink cluster status.
> The functions of these parameters are as follows:
> 1. After submitting the task through {*}flink run -Dexecution.attached=true
> xxx.jar{*}, the flink client process keeps running until the application
> cluster stops.
> 2. After submitting the task through {*}flink run -Dexecution.attached=true
> -Dexecution.shutdown-on-attached-exit=true xxx.jar{*}, the flink client can
> control the life cycle of the application cluster. When ctrl + c stops the
> flink client process, the application cluster should stop all jobs and stop
> the cluster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
