[
https://issues.apache.org/jira/browse/FLINK-16605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yangze Guo closed FLINK-16605.
------------------------------
Release Note:
With FLINK-16605, user could define the maximum number of slots through
"slotmanager.number-of-slots.max" that the Flink cluster allocates.
This is meant for limiting the resource consumption for batch workloads. It is
not recommended to configure this option for streaming workloads, which may
fail if there are not enough slots. Note that this configuration option does
not take effect for standalone clusters, where how many slots are allocated is
not controlled by Flink.
Resolution: Fixed
> Add max limitation to the total number of slots
> -----------------------------------------------
>
> Key: FLINK-16605
> URL: https://issues.apache.org/jira/browse/FLINK-16605
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Coordination
> Reporter: Yangze Guo
> Assignee: Yangze Guo
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As discussed in FLINK-15527 and FLINK-15959, we propose to add the max limit
> to the total number of slots.
> To be specific:
> - Introduce "cluster.number-of-slots.max" configuration option with default
> value MAX_INT
> - Make the SlotManager respect the max number of slots, when exceeded, it
> would not allocate resource anymore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
