[
https://issues.apache.org/jira/browse/FLINK-20748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322889#comment-17322889
]
Flink Jira Bot commented on FLINK-20748:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Remap excess slots to outstanding requirements
> ----------------------------------------------
>
> Key: FLINK-20748
> URL: https://issues.apache.org/jira/browse/FLINK-20748
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.13.0
> Reporter: Chesnay Schepler
> Assignee: Nicholas Jiang
> Priority: Major
> Labels: stale-assigned
> Fix For: 1.13.0
>
>
> The {{DeclarativeSlotPool}} maintains a mapping of slots to requirements that
> they fulfill. This mapping is currently determined when the slot is offered
> to the pool, and is only modified if the scheduler reserves this slot for a
> different requirement.
> This currently implies 2 things:
> * a slot can be prematurely released, although it could fulfill a different
> outstanding requirement
> * a new slot could be requested, despite there being another slot around
> that could fulfill the requirement
> We should remedy this by checking whether excess slots can be re-mapped to a
> different requirement, whenever the requirements change or a slot is freed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
