[
https://issues.apache.org/jira/browse/FLINK-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736127#comment-14736127
]
ASF GitHub Bot commented on FLINK-2591:
---------------------------------------
Github user willmiao commented on the pull request:
https://github.com/apache/flink/pull/1107#issuecomment-138774833
Hi rmetzger,
I've got a question: what if yarn.defaultNumberOfTaskManagers is set to a
invalid value, say -2? Should users have to supply the -n argument?
I was thinking this behavior may be appropriate:
If yarn.defaultNumberOfTaskManagers < 1 (not set or invalide value): users
have to supply the -n argument.
else if the user specified -n, the value of -n will have priority.
else, yarn.defaultNumberOfTaskManagers value will be used by default.
What do you think?
> Add configuration parameter for default number of yarn containers
> -----------------------------------------------------------------
>
> Key: FLINK-2591
> URL: https://issues.apache.org/jira/browse/FLINK-2591
> Project: Flink
> Issue Type: Improvement
> Components: YARN Client
> Reporter: Robert Metzger
> Assignee: Will Miao
> Priority: Minor
> Labels: starter
>
> A user complained about the requirement to always specify the number of yarn
> containers (-n) when starting a job.
> Adding a configuration value with a default value will allow users to set a
> default ;)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
