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 C0256200B8E for ; Mon, 26 Sep 2016 14:30:24 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BEBC9160AE3; Mon, 26 Sep 2016 12:30:24 +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 10157160AB8 for ; Mon, 26 Sep 2016 14:30:23 +0200 (CEST) Received: (qmail 25575 invoked by uid 500); 26 Sep 2016 12:30:23 -0000 Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.apache.org Delivered-To: mailing list dev@falcon.apache.org Received: (qmail 25564 invoked by uid 99); 26 Sep 2016 12:30:23 -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; Mon, 26 Sep 2016 12:30:23 +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 C3D3AC0EEE for ; Mon, 26 Sep 2016 12:30:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -5.446 X-Spam-Level: X-Spam-Status: No, score=-5.446 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id ooykXdzpmvOn for ; Mon, 26 Sep 2016 12:30:22 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id 9F9B85F36A for ; Mon, 26 Sep 2016 12:30:21 +0000 (UTC) Received: (qmail 25245 invoked by uid 99); 26 Sep 2016 12:30:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Sep 2016 12:30:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E98ED2C2AB7 for ; Mon, 26 Sep 2016 12:30:20 +0000 (UTC) Date: Mon, 26 Sep 2016 12:30:20 +0000 (UTC) From: "Praveen Adlakha (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (FALCON-2152) falcon might not start because of BacklogEmitterService MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 26 Sep 2016 12:30:24 -0000 Praveen Adlakha created FALCON-2152: --------------------------------------- Summary: falcon might not start because of BacklogEmitterService Key: FALCON-2152 URL: https://issues.apache.org/jira/browse/FALCON-2152 Project: Falcon Issue Type: Improvement Reporter: Praveen Adlakha Assignee: Praveen Adlakha Hi All, Falcon might not initialise correctly in case when a process gets deleted and is not deleted from the DB Backlog Emitter service will fail to initialize and will throw an error entity does not exist in the config store. It's a corner case and should not happen as we are deleting the entries in entitySLAMonitoring Service but it can happen in case that code fails. Thanks Praveen -- This message was sent by Atlassian JIRA (v6.3.4#6332)