apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vlad Rozov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (APEXCORE-624) Shutdown does not work because of incorrect logic in the AppMaster
Date Sat, 25 Feb 2017 01:42:44 GMT

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

Vlad Rozov resolved APEXCORE-624.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 3.4.1
                   3.6.0
                   3.5.1
                   3.2.2
                   3.3.1

> 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
>             Fix For: 3.3.1, 3.2.2, 3.5.1, 3.6.0, 3.4.1
>
>
> 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)

Mime
View raw message