[
https://issues.apache.org/jira/browse/SAMZA-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanil Jain resolved SAMZA-2361.
-------------------------------
Resolution: Fixed
> Revert Request Expiry check for Host affinity disabled cases
> -------------------------------------------------------------
>
> Key: SAMZA-2361
> URL: https://issues.apache.org/jira/browse/SAMZA-2361
> Project: Samza
> Issue Type: Bug
> Reporter: Sanil Jain
> Assignee: Sanil Jain
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> **Symptom: **: PR #1170 introduced expired request checking for Host Affinity
> disabled cases, however, this leads to a few problems that we might face in
> future:
> 1. In the scenarios of a cluster bounce, this might result in jobs (in either
> case of host affinity enabled & disabled cases) requesting containers from
> the ClusterResourceManager every 5 (default request expiry timeout) seconds
> if requests can't be fulfilled. Before PR #1170 this only used to happen for
> host affinity disabled jobs. This might potentially result in bringing down
> the ClusterManager.
> 2. Unless we have some performance benchmarking on RM (for Yarn as a cluster
> balancer), having a default expiry timeout of 5 seconds for all container
> requests is not justified.
> **Cause:** PR #1170
> **Fix:** We are reverting this behavior change since we have Performance
> benchmarking for Yarn
> **Tests:** N/A
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
