Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B083C18645 for ; Wed, 6 Jan 2016 21:52:43 +0000 (UTC) Received: (qmail 32747 invoked by uid 500); 6 Jan 2016 21:52:43 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 32709 invoked by uid 500); 6 Jan 2016 21:52:43 -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 32694 invoked by uid 99); 6 Jan 2016 21:52:43 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jan 2016 21:52:43 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 0AB91C2405 for ; Wed, 6 Jan 2016 21:52:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.779 X-Spam-Level: * X-Spam-Status: No, score=1.779 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Rc1CPD6tBOMJ for ; Wed, 6 Jan 2016 21:52:42 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id 211FC31AC8 for ; Wed, 6 Jan 2016 21:52:40 +0000 (UTC) Received: (qmail 32339 invoked by uid 99); 6 Jan 2016 21:52:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jan 2016 21:52:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D46852C1F62 for ; Wed, 6 Jan 2016 21:52:39 +0000 (UTC) Date: Wed, 6 Jan 2016 21:52:39 +0000 (UTC) From: "Venkat Ramachandran (JIRA)" To: dev@falcon.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FALCON-1728) Process entity definition allows multiple clusters when it has output Feed defined. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FALCON-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086353#comment-15086353 ] Venkat Ramachandran commented on FALCON-1728: --------------------------------------------- [~ajayyadava] [~pavan kumar], it makes sense and a useful feature. Quick question - if there is an output (say 'OutputFeed'), what will be the output feed entity's source and target clusters and how does replication on the output feed works? > Process entity definition allows multiple clusters when it has output Feed defined. > ------------------------------------------------------------------------------------ > > Key: FALCON-1728 > URL: https://issues.apache.org/jira/browse/FALCON-1728 > Project: Falcon > Issue Type: Bug > Components: process > Affects Versions: 0.9 > Reporter: Balu Vellanki > Assignee: Balu Vellanki > Priority: Critical > > Process XSD allows user to specify multiple clusters per process entity. I am guessing this would allow a user to run duplicate instance of the process on multiple clusters at the same time (I do not really see a need for this). When the process has an output feed defined, you can have duplicate process instances writing to same feed instance, causing data corruption/failures. The solution is to > 1. Do not allow multiple clusters per process. Let the user define a duplicate process if user wants to run duplicate instances. > OR > 2. Allow multiple clusters, but only when there is no output feed defined. > [~sriksun] please let me know if there is any other reason for allowing multiple clusters in a process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)