[
https://issues.apache.org/jira/browse/FLINK-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024949#comment-16024949
]
ASF GitHub Bot commented on FLINK-6708:
---------------------------------------
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/3982
Verified that Flink YARN sessions + HA works nicely now.
1. Started non-detached YARN session
2. Submit job
3. Kill JobManager
4. YARN session correctly messages disassociation with first JobManager
5. Failure of cluster status retrieval is correctly ignored, and session
does not abort.
6. New JobManager correctly registered, TMs correctly re-connect.
7. Job remains intact.
Logs are sane and nice (minus my comment on the "retrying" working).
> Don't let the FlinkYarnSessionCli fail if it cannot retrieve the ClusterStatus
> ------------------------------------------------------------------------------
>
> Key: FLINK-6708
> URL: https://issues.apache.org/jira/browse/FLINK-6708
> Project: Flink
> Issue Type: Improvement
> Components: YARN
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Minor
>
> The {{FlinkYarnSessionCli}} should not fail if it cannot retrieve the
> {{GetClusterStatusResponse}}. This would harden Flink's Yarn session.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
