[
https://issues.apache.org/jira/browse/FLINK-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15674631#comment-15674631
]
Maximilian Michels commented on FLINK-5081:
-------------------------------------------
Thanks for reporting! I couldn't reproduce the problem. Setting
{{yarn.maximum-failed-containers}} via the Flink config worked fine for me.
Setting the config entry via the command-line probably didn't work because the
parameter was supplied as an argument to the job jar instead of for the run
command:
{noformat}
flink run <args for run> <jar> <args for jar>
{noformat}
> unable to set yarn.maximum-failed-containers with flink one-time YARN setup
> ---------------------------------------------------------------------------
>
> Key: FLINK-5081
> URL: https://issues.apache.org/jira/browse/FLINK-5081
> Project: Flink
> Issue Type: Bug
> Components: Startup Shell Scripts
> Affects Versions: 1.1.4
> Reporter: Nico Kruber
>
> When letting flink setup YARN for a one-time job, it apparently does not
> deliver the {{yarn.maximum-failed-containers}} parameter to YARN as the
> {{yarn-session.sh}} script does. Adding it to conf/flink-conf.yaml as
> https://ci.apache.org/projects/flink/flink-docs-master/setup/yarn_setup.html#recovery-behavior-of-flink-on-yarn
> suggested also does not work.
> example:
> {code:none}
> flink run -m yarn-cluster -yn 3 -yjm 1024 -ytm 4096 <job>.jar --parallelism 3
> -Dyarn.maximum-failed-containers=100
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
