You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by GitBox <gi...@apache.org> on 2019/09/25 23:49:27 UTC

[GitHub] [samza] Sanil15 opened a new pull request #1170: Samza-2330: Handle expired resource request for Container allocator when host affinity is disabled

Sanil15 opened a new pull request #1170: Samza-2330: Handle expired resource request for Container allocator when host affinity is disabled	
URL: https://github.com/apache/samza/pull/1170
 
 
   **Summary of the problem**: Today when host affinity is not enabled & Cluster Manager does not issue the requested resources, the allocator thread keeps on looping forever, we want to add an expiry check for such requests to re-issue another ANY_HOST just in case if capacity is later added
   
   This PR introduces expiry check for container allocator when host affinity is disabled. Expiry timeout is defined by the existing config: `cluster-manager.container.request.timeout.ms` with a default of 5 mins. 
   
   **Note**: This is a Stacked PR which is the third in series of: 
   1. [SAMZA-2319: [1/2] Simplify Container Allocation logic](https://github.com/apache/samza/pull/1152)
   2. [SAMZA-2319: [2/2] Simplify Container Allocation logic : Rename AbstractContainerAllocator to ContainerAllocator](https://github.com/apache/samza/pull/1169)
   
   For the ease of reviewing please review the commits onwards from: https://github.com/apache/samza/commit/c0b036b4b212b0e5820c9598d1fbc1f82aa29960
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services