Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
In the current implementation of the OpportunisticContainerAllocatorAMService, we synchronously perform the allocation of opportunistic containers. This results in "blocking" the service at the RM when scheduling the opportunistic containers.
The OpportunisticContainerAllocator should instead asynchronously run as a separate thread.