Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-22072

Rethink UnfulfillableSlotRequestException class hierarchy

    XMLWordPrintableJSON

Details

    Description

      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.

      UnfulfillableSlotRequestException < ResourceManagerException < FlinkException
NoResourceAvailableException < JobException

      Attachments

        Issue Links

          is related to

          Sub-task - The sub-task of the issue FLINK-21403 Some tests expect to fail if parallelism cannot be met

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              chesnay Chesnay Schepler
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated: