[
https://issues.apache.org/jira/browse/FLINK-15297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998803#comment-16998803
]
Zili Chen commented on FLINK-15297:
-----------------------------------
Internally we have a new entrypoint that finished job very quickly so it
unstably encounter this issue. Anyway, no matter 250ms or 1ms the issue is
conceptually existing so that the fix is valid.
> Do not throw exception if YARN Application switched to FINISHED immediately
> after deployed in YarnClusterDescriptor#startAppMaster
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-15297
> URL: https://issues.apache.org/jira/browse/FLINK-15297
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
> Reporter: Zili Chen
> Assignee: Zili Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently we throw an exception in {{YarnClusterDescriptor#startAppMaster}}
> if we first detect {{FINISHED}} before {{RUNNING}}. However, it is possible a
> legal state that the application finished normally immediately.
> Right now we always try to connect the Dispatcher so it may be fine to throw
> the exception a bit earlier(otherwise when connect to a closed cluster an
> exception thrown also), but it is semantically wrong. Internally we have a
> code path that only required to report the ApplicationReport and it causes
> trouble.
> cc [~trohrmann] what do you think?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
