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 3B9BD200B96 for ; Wed, 21 Sep 2016 09:28:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3A5F2160ACF; Wed, 21 Sep 2016 07:28:22 +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 879EE160ADB for ; Wed, 21 Sep 2016 09:28:21 +0200 (CEST) Received: (qmail 93083 invoked by uid 500); 21 Sep 2016 07:28:20 -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 93059 invoked by uid 99); 21 Sep 2016 07:28:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Sep 2016 07:28:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 86C042C2A65 for ; Wed, 21 Sep 2016 07:28:20 +0000 (UTC) Date: Wed, 21 Sep 2016 07:28:20 +0000 (UTC) From: "Nagarjun Guraja (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLINK-4596) RESTART_STRATEGY is not really pluggable MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 21 Sep 2016 07:28:22 -0000 [ https://issues.apache.org/jira/browse/FLINK-4596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nagarjun Guraja updated FLINK-4596: ----------------------------------- Description: Standalone cluster config accepts an implementation(class) as part of the yaml config file but that does not work either as cluster level restart strategy or streaming job level restart strategy CLUSTER LEVEL CAUSE: createRestartStrategyFactory converts configured value of strategyname to lowercase and searches for class name using lowercased string. JOB LEVEL CAUSE: Checkpointed streams have specific code to add fixeddelayrestartconfiguration if no RestartConfiguration is specified in the job env. Also, jobs cannot provide their own custom restart strategy implementation and are constrained to pick up one of the three restart strategies provided by flink. FIX: Do not lower case the strategy config value, support a new restartconfiguration to fallback to cluster level restart strategy and support jobs to provide custom implementation of the strategy class itself. was: CAUSE: createRestartStrategyFactory converts configured value of strategyname to lowercase and searches for class name using lowercased string. FIX: Do not lower case the strategy config value or just lowercase for the switch case alone > RESTART_STRATEGY is not really pluggable > ---------------------------------------- > > Key: FLINK-4596 > URL: https://issues.apache.org/jira/browse/FLINK-4596 > Project: Flink > Issue Type: Bug > Reporter: Nagarjun Guraja > > Standalone cluster config accepts an implementation(class) as part of the yaml config file but that does not work either as cluster level restart strategy or streaming job level restart strategy > CLUSTER LEVEL CAUSE: createRestartStrategyFactory converts configured value of strategyname to lowercase and searches for class name using lowercased string. > JOB LEVEL CAUSE: Checkpointed streams have specific code to add fixeddelayrestartconfiguration if no RestartConfiguration is specified in the job env. Also, jobs cannot provide their own custom restart strategy implementation and are constrained to pick up one of the three restart strategies provided by flink. > FIX: Do not lower case the strategy config value, support a new restartconfiguration to fallback to cluster level restart strategy and support jobs to provide custom implementation of the strategy class itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)