Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4349C200C16 for ; Thu, 26 Jan 2017 01:25:31 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 41D45160B4E; Thu, 26 Jan 2017 00:25:31 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 90EC6160B5F for ; Thu, 26 Jan 2017 01:25:30 +0100 (CET) Received: (qmail 96662 invoked by uid 500); 26 Jan 2017 00:25:29 -0000 Mailing-List: contact dev-help@apex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.apache.org Delivered-To: mailing list dev@apex.apache.org Received: (qmail 96462 invoked by uid 99); 26 Jan 2017 00:25:29 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jan 2017 00:25:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 5452F1A0446 for ; Thu, 26 Jan 2017 00:25:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id vASwBGAaYLDQ for ; Thu, 26 Jan 2017 00:25:28 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 0876F5F472 for ; Thu, 26 Jan 2017 00:25:28 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 1C163E040D for ; Thu, 26 Jan 2017 00:25:27 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 720AB2528B for ; Thu, 26 Jan 2017 00:25:26 +0000 (UTC) Date: Thu, 26 Jan 2017 00:25:26 +0000 (UTC) From: "Sanjay M Pujare (JIRA)" To: dev@apex.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (APEXCORE-624) Shutdown does not work because of incorrect logic in the AppMaster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 26 Jan 2017 00:25:31 -0000 Sanjay M Pujare created APEXCORE-624: ---------------------------------------- Summary: 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: Critical 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.4#6332)