falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pallavi-rao <...@git.apache.org>
Subject [GitHub] falcon pull request: FALCON-1847 Execution order not honored when ...
Date Mon, 07 Mar 2016 11:20:51 GMT
GitHub user pallavi-rao opened a pull request:


    FALCON-1847 Execution order not honored when instances are suspended/resumed

    Have made the following changes:
    1. Order of instances on which we perform action is sorted in desc only for status and
params. Else, older instances should be suspended/resumed first.
    2. Status is now read from DB and only additional info is obtained from Oozie.
    3. Listening to suspend notification too, so further instances can be scheduled.
    4. Resume does not immediately resume the instance in order to honor concurrency.

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

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

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


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

    This closes #64
commit 9cd1249b190c3688a8069c536f9310bb75547c8f
Author: Pallavi Rao <pallavi.rao@inmobi.com>
Date:   2016-03-07T10:25:19Z

    FALCON-1847 Execution order not honored when instances are suspended/resumed

commit 069c223a21109779f5a587a98cd3bb6e3cc5f92c
Author: Pallavi Rao <pallavi.rao@inmobi.com>
Date:   2016-03-07T11:19:48Z

    FALCON-1847 Fixing the IT


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message