You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/17 09:01:00 UTC

[jira] [Commented] (FALCON-2335) Entity update should not lock the cluster entity

    [ https://issues.apache.org/jira/browse/FALCON-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440634#comment-16440634 ] 

ASF GitHub Bot commented on FALCON-2335:
----------------------------------------

GitHub user pallavi-rao opened a pull request:

    https://github.com/apache/falcon/pull/409

    FALCON-2335 Entity update should not lock the cluster entity

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/pallavi-rao/falcon 2335

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/falcon/pull/409.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #409
    
----
commit f2b4e60326833d242135827dd8e1a621d2bf4a3f
Author: pallavi-rao <pa...@...>
Date:   2018-04-17T08:58:50Z

    FALCON-2335 Entity update should not lock the cluster entity

----


> Entity update should not lock the cluster entity
> ------------------------------------------------
>
>                 Key: FALCON-2335
>                 URL: https://issues.apache.org/jira/browse/FALCON-2335
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Pallavi Rao
>            Assignee: Pallavi Rao
>            Priority: Minor
>
> Multiple entities (feeds/processes) belonging to a cluster cannot be updated simultaneously, as a cluster lock is obtained during update. This lock is unnecessary, unless the cluster itself is being update.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)