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

Unify NoAvailableResourceException handling on ExecutionGraph

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.0
    • Fix Version/s: 1.3.0
    • Labels:
      None

      Description

      Currently, there are to ways that a NoAvailableResourcesException can be handled:

      • It is either thrown synchronously, when trying to obtain a slot from the Scheduler
      • Or it is returned via an exceptionally completed Future, if the allocation completed asynchronously in the SlotPool.

      Since both cases work with futures (some eagerly completed), we should drop the path where the allocation method throws the exception directly and only keep the more general path with exceptionally completed Future.

        Issue Links

          Activity

          Hide
          StephanEwen Stephan Ewen added a comment -

          Fixed in 3bde6ffb6f55ec7ff807633ab1e79d9238e5a942

          Show
          StephanEwen Stephan Ewen added a comment - Fixed in 3bde6ffb6f55ec7ff807633ab1e79d9238e5a942

            People

            • Assignee:
              StephanEwen Stephan Ewen
              Reporter:
              StephanEwen Stephan Ewen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development