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 4424E200CD1 for ; Wed, 26 Jul 2017 16:16:02 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 42B40168E62; Wed, 26 Jul 2017 14:16:02 +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 6226C168E63 for ; Wed, 26 Jul 2017 16:16:01 +0200 (CEST) Received: (qmail 70315 invoked by uid 500); 26 Jul 2017 14:16:00 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list user@flink.apache.org Received: (qmail 70285 invoked by uid 99); 26 Jul 2017 14:15:59 -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; Wed, 26 Jul 2017 14:15:59 +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 83912183326 for ; Wed, 26 Jul 2017 14:15:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.379 X-Spam-Level: ** X-Spam-Status: No, score=2.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 F_PHGUKm-EfD for ; Wed, 26 Jul 2017 14:15:57 +0000 (UTC) Received: from mail-pg0-f41.google.com (mail-pg0-f41.google.com [74.125.83.41]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id C35DE5F30C for ; Wed, 26 Jul 2017 14:15:56 +0000 (UTC) Received: by mail-pg0-f41.google.com with SMTP id 123so84906109pgj.1 for ; Wed, 26 Jul 2017 07:15:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version; bh=VRURw1751YRKMZq3Xzd0RCTUtgGREChBMmJIZvCX0GQ=; b=qSQ79TcD5NyRBLS5vQdCnyivcbcNOLXgSlN3rtD1EU1oL2Yp4nVleuXtofEMFgCuqX FOB2s6de1LVR5n8xr4xgurg2rFPdZIUDmKWx+QajnBfk3H6PnU0jLtQ1msXaBplilBue DeCrFuH6FhKIGGh3fjlmVTSkNnWIUTaWMt5wdthL0TM+k5DcldPWRKuSD5gww4WnZwfK 5RC6GSMvDD+9HO+UvK6oic7YBIalnOz+Bml3sZx8dglDkdyWZdZigsCl3gOkuWs1mtHa TlDF890nX2F1ZxM53n+tmyEwoRJN4eGEPxBlAjP3SOKkl8umXoACWCXYpzZQUw+yVEyc lq3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version; bh=VRURw1751YRKMZq3Xzd0RCTUtgGREChBMmJIZvCX0GQ=; b=dIEy+7CGwVtcRefSwSUyqCU2Wf+uVAWJ33FUeUzEYbehw8AJnMy4K9SHy/E7lyzWHp /3hddfx8iejylQM4ODBcQj8TeRTpfUfSmOYarlsIpr6P7CfWMvu9NUgRG1vnsV7bhQYV O2zr4ixBvUC8tjh6iNSWhGrvV7Rd4MCmjCxfKSL+rCl2VXPImVmUy8ZHebmrMf1iPlwP wsQ7ScY7fMkz/sdEYRLv1Z6krT71sOeZyG4050i72LJ17ZxaiIJilCxsDHONEJEtu1n9 RCW8xoSVTRPiHF2vNbutx/J388DGeyFLETMxaTY/064iC9UgSsEMuwadywek8oLXjYQm usJA== X-Gm-Message-State: AIVw111gt/rEfI6B+sOFY9hFKRGX7dtVICg5C3uKgZcnYhNTmMtXVN6l VhuCpk3y0S8IhNxOdnQ= X-Received: by 10.98.0.71 with SMTP id 68mr998467pfa.100.1501078555443; Wed, 26 Jul 2017 07:15:55 -0700 (PDT) Received: from Ivans-MBP-2.lan (220-253-202-21.dyn.iinet.net.au. [220.253.202.21]) by smtp.gmail.com with ESMTPSA id v128sm27844899pgv.49.2017.07.26.07.15.53 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Jul 2017 07:15:54 -0700 (PDT) To: user@flink.apache.org From: Ivan Subject: is there ways to enable checkpoint from flink-conf.yaml? Message-ID: <64d344f7-e026-0645-a073-17ddfbf292cc@gmail.com> Date: Wed, 26 Jul 2017 22:15:51 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------7741AAE38357A56D2F9F14E3" archived-at: Wed, 26 Jul 2017 14:16:02 -0000 This is a multi-part message in MIME format. --------------7741AAE38357A56D2F9F14E3 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi , Flink users we are using Flink as the runtime of our beam jobs which works great, recently we want to enable restart strategy in our flink cluster, from the document I see restart strategy will only work when checkpointing is enabled. I'm trying to find out if it's possible to enable checkpointing from flink-conf.yaml which is equivalent to the call " flinkStreamEnv.enableCheckpointing(checkpointInterval);" in StreamExecutionEnvironment. the reason we want to config it through flink-conf.yaml is that we use helm to create flink cluster ondemand for dedicated job which works great on kubernetes env. with beam if we want to enable checkpointing , we have to create FlinkPipelineOptions which is cross platform. (like you use Hibernate Session in JPA code). so we are trying to find a way to enable it from flink-conf.yaml . sample flink-conf.yaml as below. flink-conf.yaml: | blob.server.port: 6124 jobmanager.rpc.address: address-cache-flink-jobmanager jobmanager.rpc.port: 6123 jobmanager.heap.mb: 256 taskmanager.heap.mb: 756 taskmanager.numberOfTaskSlots: 4 parallelism.default: 16 metrics.reporters: prom metrics.reporter.prom.class: org.apache.flink.metrics.prometheus.PrometheusReporter metrics.reporter.prom.port: 9100-9101 metrics.reporter.prom.prefix: flink_jm_ restart-strategy: fixed-delay restart-strategy.fixed-delay.attempts: 3 restart-strategy.fixed-delay.delay: 300 s state.backend: filesystem state.backend.fs.checkpointdir: file:///var/nfs/ephem_store/flink/checkpoints --------------7741AAE38357A56D2F9F14E3 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hi , Flink users

we are using Flink as the runtime of our beam jobs which works great, recently we want to enable restart strategy in our flink cluster, from the document I see restart strategy will only work when checkpointing is enabled. I'm trying to find out if it's possible to enable checkpointing from flink-conf.yaml which is equivalent to the call " flinkStreamEnv.enableCheckpointing(checkpointInterval);" in StreamExecutionEnvironment.

the reason we want to config it through flink-conf.yaml is that we use helm to create flink cluster ondemand for dedicated job which works great on kubernetes env. with beam if we want to enable checkpointing , we have to create FlinkPipelineOptions which is cross platform. (like  you use Hibernate Session in JPA code). so we are trying to find a way to enable it from flink-conf.yaml .

sample flink-conf.yaml as below.

  flink-conf.yaml: |
    blob.server.port: 6124
    jobmanager.rpc.address: address-cache-flink-jobmanager
    jobmanager.rpc.port: 6123
    jobmanager.heap.mb: 256
    taskmanager.heap.mb: 756
    taskmanager.numberOfTaskSlots: 4
    parallelism.default: 16
    metrics.reporters: prom
    metrics.reporter.prom.class: org.apache.flink.metrics.prometheus.PrometheusReporter
    metrics.reporter.prom.port: 9100-9101
    metrics.reporter.prom.prefix: flink_jm_
    restart-strategy: fixed-delay
    restart-strategy.fixed-delay.attempts: 3
    restart-strategy.fixed-delay.delay: 300 s
    state.backend: filesystem
    state.backend.fs.checkpointdir: file:///var/nfs/ephem_store/flink/checkpoints

--------------7741AAE38357A56D2F9F14E3--