[
https://issues.apache.org/jira/browse/FLINK-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15722400#comment-15722400
]
Andrew Efimov commented on FLINK-5108:
--------------------------------------
Hi team,
I thought that in this issue we should implement:
1. ShutdownHook has to look like {{YarnClusterClient.stopAfterJob}}, to perform
{{finalizeCluster}} after all jobs are completed or gracefully turn down all
jobs(jobs cancellation)
2. "not having a shutdown hook at all" As [~mxm] mentioned, maybe there is
logic which leaves some components are not in a consistent state. Should check
it.
Does it make sense?
> Remove ClientShutdownHook during job execution
> ----------------------------------------------
>
> Key: FLINK-5108
> URL: https://issues.apache.org/jira/browse/FLINK-5108
> Project: Flink
> Issue Type: Bug
> Components: YARN Client
> Affects Versions: 1.2.0, 1.1.3
> Reporter: Maximilian Michels
> Assignee: Renkai Ge
> Priority: Blocker
> Fix For: 1.2.0
>
>
> The behavior of the Standalone mode is to not react to client interrupts once
> a job has been deployed. We should change the Yarn client implementation to
> behave the same. This avoids accidental shutdown of the job, e.g. when the
> user sends an interrupt via CTRL-C or when the client machine shuts down.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
