Hi Yang Wang: I meet the question “flink job failed because Am connection is timeout but application still running via yarn-per-job mode” the same as
https://issues.apache.org/jira/browse/FLINK-18891 I try to set execution.attached to false,Will this cause other problems？I worry Thank you 原始邮件 发件人: Yang Wang<danrtsey...@gmail.com> 收件人: dev<d...@flink.apache.org> 抄送: user<user@flink.apache.org> 发送时间: 2020年8月17日(周一) 12:52 主题: Re: flink1.10.0 set execution.attached Hi weifeng, The reason why your settings in flink-conf.yaml do not take effect is that we override the "execution.attached" in "FlinkYarnSessionCli#applyDescriptorOptionToConfig" based on the cli option. If the "-d" is specified, "execution.attached" will be set to false. Otherwise, it is true. Best, Yang 魏烽 <weif...@nequal.com<mailto:weif...@nequal.com>> 于2020年8月15日周六 下午10:51写道： Hi I try to set execution.attached: false in flink-conf.yaml,but yarn logs is true like this "2020-08-15 09:40:13,489 INFO org.apache.flink.configuration.GlobalConfiguration - Loading configuration property: execution.attached, true".Can you tell me why,I see the code the default value is false,I don't know why the logs is true. The flink-conf.yaml is: execution.attached: false Buy yarn logs is: 2020-08-15 09:40:13,489 INFO org.apache.flink.configuration.GlobalConfiguration - Loading configuration property: execution.attached, true
