[
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 stale-minor (was:
auto-deprioritized-major)
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
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, 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: Minor
> Labels: auto-deprioritized-major, stale-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)
