Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Wed, 6 May 2015 15:01:00 +0000 (UTC)
From: "Mahak (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12827435.1430861093000.24096.1430924460213@Atlassian.JIRA>
In-Reply-To: <JIRA.12827435.1430861093000@Atlassian.JIRA>
References: <JIRA.12827435.1430861093000@Atlassian.JIRA>
 <JIRA.12827435.1430861093776@arcas>
Subject: [jira] [Resolved] (FALCON-1196) Partial submission of cluster.xml
 on Prism
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/FALCON-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mahak resolved FALCON-1196.
---------------------------
    Resolution: Fixed

> Partial submission of cluster.xml on Prism
> ------------------------------------------
>
>                 Key: FALCON-1196
>                 URL: https://issues.apache.org/jira/browse/FALCON-1196
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Mahak
>
> When Prism fails to submit a cluster on some falcon instances, the changes on the successful servers aren't rolled back. So if one queries any of those successful servers locally the clusters show up in the list. 
> This behavior is irrespective of if the falcon instance in the colo, the cluster.xml is written for, was successful or not.
> This doesn't really throw any exceptions/errors on later submission of the same cluster. However, may result in logical fallacies if one were to locally query such a partially updated server.
> I'm not sure if the same behavior is exhibited when submitting feeds/processes. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)