You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Venkatesh Kottapalli (JIRA)" <ji...@apache.org> on 2016/11/10 00:28:58 UTC
[jira] [Comment Edited] (APEXCORE-471) Requests for container
allocation are not resubmitted
[ https://issues.apache.org/jira/browse/APEXCORE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652496#comment-15652496 ]
Venkatesh Kottapalli edited comment on APEXCORE-471 at 11/10/16 12:28 AM:
--------------------------------------------------------------------------
In the issue scenario, there are other jobs using 177 containers from 180 containers in the cluster. When the Apex job is launched, it needs 20 containers and received the 3 remaining containers in the cluster initially.
After this, there is no request from the App master to RM to get the rest of the 17 resources allocated and the job waits in pending state forever.
was (Author: venkatesh kottapalli):
In the issue scenario, there are other jobs using 177 containers from 180 containers in the cluster. When the Apex job is launched, it needs 20 containers and received the 3 remaining containers in the cluster initially.
After this, there is no request from the App master to RM to get the rest of the 17 resources allocated and the job waits in pending state forever even after the other jobs in the cluster got completed and all the containers are available.
> Requests for container allocation are not resubmitted
> -----------------------------------------------------
>
> Key: APEXCORE-471
> URL: https://issues.apache.org/jira/browse/APEXCORE-471
> Project: Apache Apex Core
> Issue Type: Bug
> Affects Versions: 3.3.0, 3.4.0
> Reporter: Vlad Rozov
>
> When Yarn cluster has a limited number of available resources, requests should be resubmitted. BlacklistBasedResourceRequestHandler does not properly handle case when resources are limited.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)