PrabhuJoseph opened a new pull request, #22870:
URL: https://github.com/apache/flink/pull/22870

   ## What is the purpose of the change
   
   Currently, Blocklist unblockResources does not update the existing pending 
resource request from YARN/K8S. It updates only for the new resource requests. 
The existing pending resource requests are not scheduled on the nodes which are 
unblocked. This Patch updates the pending resource requests.
   
   
   ## Brief change log
   
   1. _unblockResources_ method is added in _ResourceManagerDriver_ interface 
which both _YarnResourceManagerDriver_ and _KubernetesResourceManagerDriver_ 
implements.
   2. _ActiveResourceManager_ invokes the _unblockResources_ in 
_ResourceManagerDriver_ when _BlockListHandler_ removes the timedout blocked 
nodes.
   3. _YarnResourceManagerDriver_ calls the _tryUpdateApplicationBlockList_ to 
update YARN with new block list details.
   4. _KubernetesResourceManagerDriver_ gets the pending pod with node affinity 
notin set to any of the unblocked node and stops and reschedule.
   
   
   ## Verifying this change
   
   1. _YarnResourceManagerDriverTest_#_testUpdateBlocklist_
   2. _KubernetesResourceManagerDriverTest_#_testUnblockResources_
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): **(no)**
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: **(no)**
     - The serializers: **(no)**
     - The runtime per-record code paths (performance sensitive): **(no)**
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: **(no)**
     - The S3 file system connector: **(no)**
   
   ## Documentation
   
     - Does this pull request introduce a new feature?  **(no)**
     - If yes, how is the feature documented? **(not applicable)**
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to