[
https://issues.apache.org/jira/browse/FALCON-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182893#comment-15182893
]
ASF GitHub Bot commented on FALCON-1847:
----------------------------------------
GitHub user pallavi-rao opened a pull request:
https://github.com/apache/falcon/pull/64
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:
https://github.com/apache/falcon/pull/64.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 #64
----
commit 9cd1249b190c3688a8069c536f9310bb75547c8f
Author: Pallavi Rao <[email protected]>
Date: 2016-03-07T10:25:19Z
FALCON-1847 Execution order not honored when instances are suspended/resumed
commit 069c223a21109779f5a587a98cd3bb6e3cc5f92c
Author: Pallavi Rao <[email protected]>
Date: 2016-03-07T11:19:48Z
FALCON-1847 Fixing the IT
----
> Execution order not honored when instances are suspended/resumed
> ----------------------------------------------------------------
>
> Key: FALCON-1847
> URL: https://issues.apache.org/jira/browse/FALCON-1847
> Project: Falcon
> Issue Type: Bug
> Affects Versions: 0.9
> Reporter: Pallavi Rao
> Assignee: Pallavi Rao
> Fix For: trunk
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
