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 5358E200C05 for ; Mon, 23 Jan 2017 11:30:30 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 51D52160B58; Mon, 23 Jan 2017 10:30:30 +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 A515D160B49 for ; Mon, 23 Jan 2017 11:30:29 +0100 (CET) Received: (qmail 67268 invoked by uid 500); 23 Jan 2017 10:30:28 -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 67257 invoked by uid 99); 23 Jan 2017 10:30:28 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jan 2017 10:30:28 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 2C3B4C0EE5 for ; Mon, 23 Jan 2017 10:30:28 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 4e90jvGHobkW for ; Mon, 23 Jan 2017 10:30:27 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 647FF5F649 for ; Mon, 23 Jan 2017 10:30:27 +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 B5A65E0238 for ; Mon, 23 Jan 2017 10:29:26 +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 6D2CB25285 for ; Mon, 23 Jan 2017 10:29:26 +0000 (UTC) Date: Mon, 23 Jan 2017 10:29:26 +0000 (UTC) From: "Tushar Gosavi (JIRA)" To: dev@apex.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (APEXCORE-619) recovery window id in future for terminating state less operators during relaunch. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 23 Jan 2017 10:30:30 -0000 Tushar Gosavi created APEXCORE-619: -------------------------------------- Summary: recovery window id in future for terminating state less operators during relaunch. Key: APEXCORE-619 URL: https://issues.apache.org/jira/browse/APEXCORE-619 Project: Apache Apex Core Issue Type: Bug Reporter: Tushar Gosavi Assignee: Tushar Gosavi With following DAG A -> B -> C C is a stateless operator. If this application is killed and restarted after long time between kill and restart, then recovery window id of C is too high compare to A and B. This is because recovery windowid is computed from current timestamp for stateless operators in updateRecoveryCheckpoints. The problem this causes - Operator C does not process any data till windowId of B reached to recovery window id of C. - If other operators are not able to keep up then C gets killed because it is detected as blocked operator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)