-
Notifications
You must be signed in to change notification settings - Fork 749
[GOBBLIN-1974] Ensure Adhoc Flows can be Executed in Multi-active Scheduler state #3846
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 2 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
908935e
Ensure Adhoc Flows can be Executed in Multi-active Scheduler state
a60aa94
Only delete spec for adhoc flows & always after orchestration
43857dd
Delete adhoc flows when dagManager is not present as well
1663ef1
Fix flaky test for scheduler
c1fd282
Add clarifying comment about failure recovery
0b99c4b
Re-ordered private method
486cae6
Move private methods again
e1b722a
Enforce sequential ordering of unit tests to make more reliable
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would this work for launch events of adhoc flows when a leader goes down? (i.e. need to re-compile the flow from the flow catalog in the dag action change monitor).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it will. If we've gotten to the point where
addDagpersists thedagtodagStateStore, now its responsibility ofdagManagerto execute it. The multi-active scheduler component ensures persisting todagActionStoreso the event will not be reprocessed throughdagActionChangeMonitor. ThedagActionChangeMonitoronly commits the offset after submitting a launch event to theOrchestratorfor compiling and completing theaddDagcall. The new leader'sDagManagerwill recover it fromDagStateStoreif the old leader never completes it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great news! let's consider a code comment to preserve this knowledge