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

Posted to dev@apex.apache.org by "Vlad Rozov (JIRA)" <ji...@apache.org> on 2017/02/12 21:56:41 UTC

[jira] [Updated] (APEXCORE-624) Shutdown does not work because of incorrect logic in the AppMaster

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

Vlad Rozov updated APEXCORE-624:
--------------------------------
    Priority: Minor  (was: Major)

> Shutdown does not work because of incorrect logic in the AppMaster
> ------------------------------------------------------------------
>
>                 Key: APEXCORE-624
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-624
>             Project: Apache Apex Core
>          Issue Type: Bug
>            Reporter: Sanjay M Pujare
>            Assignee: Sanjay M Pujare
>            Priority: Minor
>
> com.datatorrent.stram.StreamingAppMasterService.execute() calculates numRequestedContainers incorrectly in some cases (e.g. RM container allocation failure) which prevents an application from shutting down when it is requested externally. An example is where we ask RM to remove previous container allocation request (where the count should be decremented but is NOT) and add a new one (where the count should be and IS incremented). Another example is the "alreadyAllocated" case where we release the container and still increment numRequestedContainers which seems wrong. 
> This bug is showing up in multiple Apex deployments.



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