-
Notifications
You must be signed in to change notification settings - Fork 17.4k
Make RedshiftDeleteClusterOperator delete reliably during cluster transitions #69574
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
Open
seanghaeli
wants to merge
4
commits into
apache:main
Choose a base branch
from
aws-mwaa:feature/redshift-delete-deferrable-wait
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
bf712ff
Make RedshiftDeleteClusterOperator delete reliably during cluster tra…
230a232
Trim verbose docstrings in redshift delete operator/trigger
58f8d30
Trim over-explanatory comments in redshift delete execute/init
10122f7
Add 'deletable' to spelling wordlist
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -449,6 +449,7 @@ deferrable | |
| deidentify | ||
| DeidentifyTemplate | ||
| del | ||
| deletable | ||
| delim | ||
| deliverability | ||
| deltalake | ||
|
|
||
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
Oops, something went wrong.
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.
This might not work if
_retry_delete_when_settledis executed on a different machine/host thanexecute. If some random values are passed to the construct ofRedshiftDeleteClusterOperator, then some values will differ betweenexecuteand_retry_delete_when_settled. For example, if a random number is used to definecluster_identifier, then definitely this will failThere 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.
I believe the exact same pattern is used here in EKS:
airflow/providers/amazon/src/airflow/providers/amazon/aws/operators/eks.py
Line 401 in e546579
I am going to investigate if this causes a fail but I think if this is an issue in this PR, it's also a latent issue in EKS currently
Uh oh!
There was an error while loading. Please reload this page.
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.
@vincbeck I just tried the resume step from a different worker than the one that tries the first delete (which fails because the cluster is not in a ready state yet), and it still succeeds.
RedshiftDeleteClusterOperatorin deferrable modepid 738ranexecutewhile cluster was still mid-transition so it defers.pid 968successfully deleted the cluster.I believe this is fine because the
cluster_identifieris serialized in the trigger's init, so it persists in the metastore when the new worker reads it. Here's where it gets serialized:airflow/task-sdk/src/airflow/sdk/execution_time/task_runner.py
Lines 1453 to 1457 in e546579
^ where
cluster_identifieris included intrigger_kwargs