You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Pallavi Rao (JIRA)" <ji...@apache.org> on 2016/06/07 06:20:21 UTC

[jira] [Created] (FALCON-2014) Issue with submit idempotency in distributed mode

Pallavi Rao created FALCON-2014:
-----------------------------------

             Summary: Issue with submit idempotency in distributed mode
                 Key: FALCON-2014
                 URL: https://issues.apache.org/jira/browse/FALCON-2014
             Project: Falcon
          Issue Type: Bug
            Reporter: Pallavi Rao


Lets say, a user submits an entity, entity1, against cluster1 and cluster2. 

Later, he submits the same entity, but with a different definition, against cluster3. Prism routes the request to cluster3 Falcon server. Since that server does not have entity1, it updates its config store (with a new definition).

However, prism later fails the submit after a definition check (as it does not match with prev definition). Now, prism, cluster1 and cluster2 have definition1 and cluster3 has definition2.



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