[
https://issues.apache.org/jira/browse/FLINK-29870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song closed FLINK-29870.
--------------------------------
Resolution: Done
master (1.17): 209df810f13e2fcbe5a4ca8bb015a8a5f662adc4
> split ResourceNotEnoughNotifier from ResourceActions
> ----------------------------------------------------
>
> Key: FLINK-29870
> URL: https://issues.apache.org/jira/browse/FLINK-29870
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.16.0
> Reporter: Weihua Hu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.17.0
>
>
> SlotManager determines whether a resource can be allocated by the return
> value of ResourceActions.allocateResource. It can reduce unnecessary waiting
> by quickly marking the slotRequest as a failure if the resource cannot be
> allocated.
> The new declareResourceNeed function will not return whether resources could
> be allocated. This will cause useless waiting for SlotRequests.
> Currently, ResourceActions does only two kinds of things.
> allocate/release resource by ResourceManager, this only supported by
> ActiveResourceManager
> notify resource not enough to JobMaster
> So we can split ResourceNotEnoughNotifier from ResourceActions, and make
> ResourceActions only works for ActiveResourceManager
> ResourceNotEnoughNotifier only send notifyNotEnoughResourcesAvailable to
> JobMaster
> ResourceActions will deal with declareResourcesNeeded
> For StandaloneResourceManager, The SlotManager will not have one
> ResourceAllocator, so it can fail the SlotRequests quickly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
