[
https://issues.apache.org/jira/browse/FLINK-24063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17407933#comment-17407933
]
Aitozi commented on FLINK-24063:
--------------------------------
Thanks for your reply [~trohrmann]. I think there are two case will invoke
runCluster
* Client submit start a new job
* An old jobManager failed, and spawned a new one.
In case1: if we do not {{STOP_APPLICATION}} after failure, client may keep
waiting for the cluster to be ready ?
In case2: I think it's ok to let the job restart again by using
{{ShutdownBehaviour.STOP_PROCESS}}
The difference is that we may expect a job especially a streaming job keep
running without turning to a terminated status.
> Reconsider the behavior of ClusterEntrypoint#startCluster failure handler
> -------------------------------------------------------------------------
>
> Key: FLINK-24063
> URL: https://issues.apache.org/jira/browse/FLINK-24063
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Aitozi
> Priority: Minor
>
> If the job runCluster failed, it will trigger the STOP_APPLICATION behavior.
> But if we consider a case like that:
> # A job have running for a long time
> # Then the JobManager encounter a fatal error like the network problem,
> which may let the jobManager process down
> # Then a new process will be started by the resource framework like yarn or
> kubernetes. But it will failed at the ClusterEntrypoint#startCluster due to
> the same network problem.
> # Then the job turn into the FAILED status.
>
> This means a streaming job will no longer run due to some fatal error, this
> is somehow fragile. I think we should give some retry mechanism to prevent
> the job fast fail twice ,so that deal with some external error which may keep
> for a period of time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
