[
https://issues.apache.org/jira/browse/FLINK-19150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191594#comment-17191594
]
Jiayi Liao commented on FLINK-19150:
------------------------------------
[~aljoscha] I didn't retrieve the result with another client and I also don't
know why the connection loss happens. Do you have idea that can help to locate
the problem?
> Behaviour change after migration from 1.9 to 1.11
> -------------------------------------------------
>
> Key: FLINK-19150
> URL: https://issues.apache.org/jira/browse/FLINK-19150
> Project: Flink
> Issue Type: Bug
> Components: Client / Job Submission
> Affects Versions: 1.11.0
> Reporter: Jiayi Liao
> Priority: Major
>
> In Flink 1.9, if we submit a job in attach mode, the client will help to shut
> down the cluster in the end. While in Flink 1.11, the cluster will be shut
> down as long as the job result is requested, no matters where the request
> comes from.
> Currently we've found that the client cannot succeed to get the job execution
> result and report connection lost error because the result has already been
> requested and the cluster is shut down. The root cause is under investigation
> but we think it might be related to the network environment since the
> frequency of occurance is very low.
> I'm aware of that there's a big restructure on the job submission from Flink
> 1.9 to 1.11. But is this change expected?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
