Skip to content
This repository has been archived by the owner on Apr 4, 2021. It is now read-only.

FALCON-2113 Falcon retry happens in few cases inspite of a manual kill from the user. move it to a different state(ignore) and check for that state before retrying to stop it from retrying. #265

Closed
wants to merge 10 commits into from

Conversation

sandeepSamudrala
Copy link
Contributor

No description provided.

@sandeepSamudrala sandeepSamudrala changed the title Falcon 2113. Falcon retry happens in few cases inspite of a manual kill from the user. move it to a different state(ignore) and check for that state before retrying to stop it from retrying. Falcon-2113. Falcon retry happens in few cases inspite of a manual kill from the user. move it to a different state(ignore) and check for that state before retrying to stop it from retrying. Aug 13, 2016
@sandeepSamudrala sandeepSamudrala changed the title Falcon-2113. Falcon retry happens in few cases inspite of a manual kill from the user. move it to a different state(ignore) and check for that state before retrying to stop it from retrying. Falcon-2113 Falcon retry happens in few cases inspite of a manual kill from the user. move it to a different state(ignore) and check for that state before retrying to stop it from retrying. Aug 13, 2016
@sandeepSamudrala sandeepSamudrala changed the title Falcon-2113 Falcon retry happens in few cases inspite of a manual kill from the user. move it to a different state(ignore) and check for that state before retrying to stop it from retrying. FALCON-2113 Falcon retry happens in few cases inspite of a manual kill from the user. move it to a different state(ignore) and check for that state before retrying to stop it from retrying. Aug 13, 2016
@@ -111,7 +114,8 @@ public abstract InstancesResult getInstanceParams(Entity entity, Date start, Dat

public abstract boolean isNotificationEnabled(String cluster, String jobID) throws FalconException;

public abstract Boolean isWorkflowKilledByUser(String cluster, String jobId) throws FalconException;
public abstract Boolean isWorkflowKilledByUser(String cluster, String jobId,
String parentId) throws FalconException;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding a parent Id here makes some assumptions on the hierarchy (coord->wf) which does not hold for native workflow engine. Instead, do a WorkflowInfo to retrieve the parent inside the method.

@pallavi-rao
Copy link

+1

@sandeepSamudrala
Copy link
Contributor Author

Rebased the patch and fixed failures.

@PraveenAdlakha
Copy link
Contributor

+1

@asfgit asfgit closed this in 470f343 Aug 24, 2016
pallavi-rao pushed a commit to pallavi-rao/falcon that referenced this pull request Feb 16, 2018
…l from the user. move it to a different state(ignore) and check for that state before retrying to stop it from retrying.

Author: sandeep <sandysmdl@gmail.com>

Reviewers: @pallavi-rao, @PraveenAdlakha

Closes apache#265 from sandeepSamudrala/FALCON-2113 and squashes the following commits:

2a00bef [sandeep] fixing failures
285c796 [sandeep] Merge branch 'master' of https://github.com/apache/falcon into FALCON-2113
4f585a1 [sandeep] Incorporated review comments. Removed parent Id from passing into method to check for manual kill
2d0d9a3 [sandeep] FALCON-2113. Falcon retry happens in few cases inspite of a manual kill from the user.  move it to a different state(ignore) and check for that state before retrying to stop it from retrying.
1bb8d3c [sandeep] Merge branch 'master' of https://github.com/apache/falcon
c065566 [sandeep] reverting last line changes made
1a4dcd2 [sandeep] rebased and resolved the conflicts from master
271318b [sandeep] FALCON-2097. Adding UT to the new method for getting next instance time with Delay.
a94d4fe [sandeep] rebasing from master
9e68a57 [sandeep] FALCON-298. Feed update with replication delay creates holes
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants