[
https://issues.apache.org/jira/browse/FLINK-22072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22072:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Rethink UnfulfillableSlotRequestException class hierarchy
> ---------------------------------------------------------
>
> Key: FLINK-22072
> URL: https://issues.apache.org/jira/browse/FLINK-22072
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Coordination
> Reporter: Chesnay Schepler
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> The ResourceManager currently can throw 2 different exceptions if not enough
> slots are available:
> UnfulfillableSlotRequestException, if a slot could not be acquired, and no TM
> in the cluster could even theoretically provide it (due to the resource
> profiles not matching)
> NoResourceAvailableException, if a slot could not be acquired, because none
> are free or a task executor, that could theoretically provide it, could not
> be allocated
> Despite being fairly similar in terms of semantics, hierarchy wise these are
> completely separate.
> {code}
> UnfulfillableSlotRequestException < ResourceManagerException < FlinkException
> NoResourceAvailableException < JobException
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
