Skip to content
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

Porting signal processing to the task monitor condition for 2.10.1 #151

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

ashishgo-aws
Copy link
Contributor

The task monitor needs to process the following 4 MWAA signals for the graceful update project:

  1. Termination signal: Graceful termination of the workers when the environment is going through a graceful update
  2. Resume signal: Reverting the state of graceful termination and resume work when the environment is going through a rollback after attempting a graceful update
  3. Kill signal: Shutting down the worker without waiting for the current Airflow tasks to finish when the environment is going through a forced update
  4. Activation signal: Starting consumption of work from the queue after termination protection has enabled on the corresponding Fargate task

The processing is gated behind certain environment variables which are either absent or marked as false for an environment which does not have graceful updates enabled.

The CR brings the changes that have been merged for 2.9.2 (#137 and #150) to the newer version.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

The task monitor needs to process the following 4 MWAA signals for the graceful update project:

1. Termination signal: Graceful termination of the workers when the environment is going through a graceful update
2. Resume signal: Reverting the state of graceful termination and resume work when the environment is going through a rollback after attempting a graceful update
3. Kill signal: Shutting down the worker without waiting for the current Airflow tasks to finish when the environment is going through a forced update
4. Activation signal: Starting consumption of work from the queue after termination protection has enabled on the corresponding Fargate task

The processing is gated behind certain environment variables which are either absent or marked as false for an environment which does not have graceful updates enabled.

The CR brings the changes that have been merged for 2.9.2 (aws#137 and aws#150) to the newer version.
@ashishgo-aws ashishgo-aws self-assigned this Oct 1, 2024
@ashishgo-aws ashishgo-aws requested review from dhegberg and Kytha October 1, 2024 18:04
@ashishgo-aws ashishgo-aws changed the title Porting graceful updates image changes to 2.10.1 Porting signal processing to the task monitor condition for 2.10.1 Oct 1, 2024
@ashishgo-aws ashishgo-aws merged commit fabe3c1 into aws:main Oct 3, 2024
1 check passed
@ashishgo-aws ashishgo-aws deleted the graceful-updates-2.10 branch October 3, 2024 22:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants