[
https://issues.apache.org/jira/browse/FLINK-9326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470243#comment-16470243
]
Till Rohrmann commented on FLINK-9326:
--------------------------------------
You're right [~Sam_D]. That way the user experience out of the box is a bit
better, because it won't fail. I agree, though, that this is not very intuitive
and confusing.
Maybe we could do it that we use the {{TaskManagerOptions#NUM_TASK_SLOTS}} if
explicitly set and otherwise we default to the
{{jobGraph.getMaximumParallelism}}.
> TaskManagerOptions.NUM_TASK_SLOTS does not work for local/embedded mode
> -----------------------------------------------------------------------
>
> Key: FLINK-9326
> URL: https://issues.apache.org/jira/browse/FLINK-9326
> Project: Flink
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.5.0
> Environment: Linux 64bit
> Flink branch release-1.5
> Reporter: Samuel Doyle
> Assignee: vinoyang
> Priority: Major
>
> When attempting to set the number of task slots via the api such ash
> {code:java}
> configuration = new Configuration();
> configuration.setInteger(TaskManagerOptions.NUM_TASK_SLOTS, 16);
> configuration.setInteger(CoreOptions.DEFAULT_PARALLELISM, 1);
> {code}
> I will always end up with the default slot setting based on the number of
> cores I have where my standalone instance is running, it doesn't matter what
> I set the the NUM_TASK_SLOTS to, it has no effect
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
