[jira] [Updated] (FLINK-22072) Rethink UnfulfillableSlotRequestException class hierarchy

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-22072:
-----------------------------------
    Labels: stale-major  (was: )

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.


> 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: Major
>              Labels: stale-major
>
> 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 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.3.4#803005)