Stephan Ewen created FLINK-5766:
-----------------------------------
Summary: Unify NoAvailableResourceException handling on
ExecutionGraph
Key: FLINK-5766
URL: https://issues.apache.org/jira/browse/FLINK-5766
Project: Flink
Issue Type: Improvement
Components: Distributed Coordination
Affects Versions: 1.2.0
Reporter: Stephan Ewen
Assignee: Stephan Ewen
Fix For: 1.3.0
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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
