[ 
https://issues.apache.org/jira/browse/FLINK-20748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-20748:
-----------------------------------
    Labels: auto-unassigned stale-major  (was: auto-unassigned)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Major but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this 
ticket is a Major, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> 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
>            Priority: Major
>              Labels: auto-unassigned, stale-major
>
> 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)

Reply via email to