GitHub user pallavi-rao opened a pull request:
https://github.com/apache/falcon/pull/48
FALCON-1835 Falcon should do coord rerun rather than workflow rerun ...
â¦to ensure concurrency
Patch contains the following changes:
1. Upgrade to Oozie client 4.2 (from 4.1).
2. Remove workflow rerun completely and switch to coord rerun.
3. Introduced parentId in WorkflowExecutionContext in order to store the
coord action of a given workflow. This will be used during retry and late data
rerun.
4. In cases where parentId cannot be populated (notification from Post
processing action will not contain this), rerun method queries Oozie to
retrieve the parent id.
5. The rerun method now returns the actual status after rerun, rather than
hardcoded âRUNNINGâ.
6. In 4.2, Oozie does a Yarn job kill to kill any lingering executions of
previous run of a workflow. It uses RMClientProxy to do the same. Since in
local mode, RPC cannot happen, had to introduce LocalFalconRPCClientFactory to
prevent RPC in local mode.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pallavi-rao/falcon 1835
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/falcon/pull/48.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 #48
----
commit 43df66d56dbe4a674e6a8499b93cf7a14c076f83
Author: Pallavi Rao <[email protected]>
Date: 2016-02-23T10:38:51Z
FALCON-1835 Falcon should do coord rerun rather than workflow rerun to
ensure concurrency
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
