You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Naganarasimha G R (JIRA)" <ji...@apache.org> on 2017/02/08 01:18:41 UTC

[jira] [Assigned] (YARN-6157) Inconsistencies in verifying Max Applications

     [ https://issues.apache.org/jira/browse/YARN-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Naganarasimha G R reassigned YARN-6157:
---------------------------------------

    Assignee: Naganarasimha G R

> Inconsistencies in verifying Max Applications
> ---------------------------------------------
>
>                 Key: YARN-6157
>                 URL: https://issues.apache.org/jira/browse/YARN-6157
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
>
> Inconsistencies in verifying Max Applications when the max apps is reduced and either HA is done ow work preserving restart is done.
> # currently Max applications across cluster should not be done for the recovered apps. Seems like currently we are doing it
> #  Max applications for a queue is done @ CapacityScheduler.addApplication which considers sum of Pending and running applications but we add to pending applications in {{CapacityScheduler.addApplicationAttempt -> LeafQueue.addApplicationAttempt}} so between these 2 checks we can activate more apps than what can queue restrict.
> # During recovery of a RMApp, if applicationAttempts are not found then we recover it without recovery false @ {{RMAppImpl.RMAppRecoveredTransition}}, this can lead to failure of apps which were accepted earlier but attempt was not yet created and HA happens when MAX app configuration (for cluster/queue) is modified.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org