From issues-return-156952-archive-asf-public=cust-asf.ponee.io@flink.apache.org Mon Mar 5 18:03:03 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5B73D180608 for ; Mon, 5 Mar 2018 18:03:03 +0100 (CET) Received: (qmail 98023 invoked by uid 500); 5 Mar 2018 17:03:02 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 98014 invoked by uid 99); 5 Mar 2018 17:03:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Mar 2018 17:03:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id DB563180046 for ; Mon, 5 Mar 2018 17:03:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id mpQC4NO4XWAq for ; Mon, 5 Mar 2018 17:03:01 +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 E0FC25F475 for ; Mon, 5 Mar 2018 17:03:00 +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 13834E0295 for ; Mon, 5 Mar 2018 17:03:00 +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 1B84D21266 for ; Mon, 5 Mar 2018 17:03:00 +0000 (UTC) Date: Mon, 5 Mar 2018 17:03:00 +0000 (UTC) From: "Stefan Richter (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (FLINK-8871) Checkpoint cancellation is not propagated to stop checkpointing threads on the task manager MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Stefan Richter created FLINK-8871: ------------------------------------- Summary: Checkpoint cancellation is not propagated to stop che= ckpointing threads on the task manager Key: FLINK-8871 URL: https://issues.apache.org/jira/browse/FLINK-8871 Project: Flink Issue Type: Bug Components: State Backends, Checkpointing Affects Versions: 1.4.1, 1.3.2, 1.5.0 Reporter: Stefan Richter Fix For: 1.6.0 Flink currently lacks any form of feedback mechanism from the job manager /= checkpoint coordinator to the tasks when it comes to failing a checkpoint.= This means that running snapshots on the tasks are also not stopped even i= f their owning checkpoint is already cancelled. Two examples for cases wher= e this applies are checkpoint timeouts and local checkpoint failures on a t= ask together with a configuration that does not fail tasks on checkpoint fa= ilure.=C2=A0Notice that those=C2=A0running snapshots do=C2=A0no longer acco= unt for the maximum number of parallel checkpoints, because their owning ch= eckpoint is considered as cancelled. Not stopping the task's snapshot thread can lead to a problematic=C2=A0situ= ation where=C2=A0the next checkpoints already started, while the abandoned = checkpoint thread from a previous checkpoint is still lingering around runn= ing. This scenario can potentially cascade: many parallel checkpoints will = slow down checkpointing and make timeouts even more likely. =C2=A0 A possible solution is introducing a {{cancelCheckpoint}}=C2=A0method=C2=A0= as counterpart to the {{triggerCheckpoint}}=C2=A0method in the task manage= r gateway, which is invoked by the checkpoint coordinator as part of=C2=A0c= ancelling the checkpoint. -- This message was sent by Atlassian JIRA (v7.6.3#76005)