[
https://issues.apache.org/jira/browse/APEXCORE-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126697#comment-16126697
]
Vlad Rozov commented on APEXCORE-777:
-------------------------------------
-1 to address the issue as part of APEXCORE-771. Code refactoring moves code
around but does not change the logic. To fix the issue, it is necessary to
change the logic of how the number of requested containers is counted.
> Application Master may not shutdown due to incorrect numRequestedContainers
> counting
> ------------------------------------------------------------------------------------
>
> Key: APEXCORE-777
> URL: https://issues.apache.org/jira/browse/APEXCORE-777
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Vlad Rozov
> Priority: Minor
>
> Consider a scenario where App master requests a container from Yarn
> (numRequestedContainers = 1). There is not enough resources and the request
> timeouts. My understanding is that App master will re-request it again but
> the number of requested containers will not change (one newly requested, one
> removed). Let's assume that App master, by the time Yarn responds back
> decides that it does not need any. If Yarn responds with one allocated
> containers, numRequestedContainers will go to 0 (correct), but Yarn may
> respond back with 2 allocated containers if by the time App Master sends the
> second request it already allocated a container requested in the original
> request (the one that timeouted) as Yarn does not guarantee that removed
> request is fullfilled (see Yarn doc). Will not in this case
> numRequestedContainers be -1 due to the bulk decrement?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
