From issues-return-184329-archive-asf-public=cust-asf.ponee.io@flink.apache.org Tue Aug 14 11:48:04 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 23A6A180654 for ; Tue, 14 Aug 2018 11:48:03 +0200 (CEST) Received: (qmail 54089 invoked by uid 500); 14 Aug 2018 09:48:03 -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 54080 invoked by uid 99); 14 Aug 2018 09:48:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2018 09:48:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id BEDFBC06B7 for ; Tue, 14 Aug 2018 09:48:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id xwtQmxAN6QW4 for ; Tue, 14 Aug 2018 09:48:01 +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 3060E5F516 for ; Tue, 14 Aug 2018 09:48:01 +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 7AD9CE00D3 for ; Tue, 14 Aug 2018 09:48: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 37FC923F99 for ; Tue, 14 Aug 2018 09:48:00 +0000 (UTC) Date: Tue, 14 Aug 2018 09:48:00 +0000 (UTC) From: "Till Rohrmann (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLINK-10074) Allowable number of checkpoint failures MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLINK-10074?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D165= 79555#comment-16579555 ]=20 Till Rohrmann commented on FLINK-10074: --------------------------------------- Since {{setFailOnCheckpointingErrors}} is public, we cannot simply change i= ts signature. What we could do though, is to add another method {{setNumber= TolerableCheckpointFailures(int)}} which is set by default to {{0}} and is = only respected if {{setFailOnCheckpointingErrors}} is set to {{true}}. So i= f the the user on calls {{setFailOnCheckpointingErrors(true)}} then he will= get the same old behaviour. Only after calling {{setNumberTolerableCheckpo= intFailures(10)}}, it will wait for 10 checkpoint failures before failing. = If {{setNumberTolerableCheckpointFailures}} is set but {{setFailOnCheckpoin= tingErrors(false)}}, then checkpoint failures won't fail the job. [~thw] would you not reset the counter in case of a restart? This would be = hard to do in case of a JobManager failover and lead to different behaviour= s depending on the actual fault. > Allowable number of checkpoint failures=20 > ---------------------------------------- > > Key: FLINK-10074 > URL: https://issues.apache.org/jira/browse/FLINK-10074 > Project: Flink > Issue Type: Improvement > Components: State Backends, Checkpointing > Reporter: Thomas Weise > Assignee: vinoyang > Priority: Major > > For intermittent checkpoint failures it is desirable to have a mechanism = to avoid restarts. If, for example, a transient S3 error prevents checkpoin= t completion, the next checkpoint may very well succeed. The user may wish = to not incur the expense of restart under such scenario and this could be e= xpressed with a failure threshold (number of subsequent checkpoint failures= ), possibly combined with a list of exceptions to tolerate. > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)