You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Sanil Jain (Jira)" <ji...@apache.org> on 2019/11/27 02:20:00 UTC

[jira] [Commented] (SAMZA-2330) Handle expired resource request for Container allocator when host affinity is disabled

    [ https://issues.apache.org/jira/browse/SAMZA-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16983098#comment-16983098 ] 

Sanil Jain commented on SAMZA-2330:
-----------------------------------

This patch was reverted because of absence of Benchmarking on RM for handling requests

> Handle expired resource request for Container allocator when host affinity is disabled
> --------------------------------------------------------------------------------------
>
>                 Key: SAMZA-2330
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2330
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Sanil Jain
>            Assignee: Sanil Jain
>            Priority: Major
>
> Today when host affinity is not enabled & Cluster Manager does not issue the requested resources, the allocator thread keeps on waiting forever, we want to add an expiry check for such requests to re-issue another ANY_HOST just in case if capacity is available



--
This message was sent by Atlassian Jira
(v8.3.4#803005)