You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2021/03/31 15:02:00 UTC

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

Chesnay Schepler created FLINK-22072:
----------------------------------------

             Summary: Rethink UnfulfillableSlotRequestException class hierarchy
                 Key: FLINK-22072
                 URL: https://issues.apache.org/jira/browse/FLINK-22072
             Project: Flink
          Issue Type: Bug
          Components: Runtime / Coordination
            Reporter: Chesnay Schepler
             Fix For: 1.14.0


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)