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

feat(taskworker): Make hybridcloud taskworker compatible #88824

Merged
merged 1 commit into from
Apr 4, 2025

Conversation

enochtangg
Copy link
Member

This work is required to migrate tasks from celery to the new taskbroker system. The sentry option will be used to control the rollout of these tasks. The full migration plan is describe in this document.

Notable changes/callouts
Most of relocation tasks use retry_backof, retry_backoff_jitter, and soft_time_limit which taskworker does not support
LastAction (action taken when retries are exhausted) is set to discard
sentry.relocation.fulfill_cross_region_export_request uses reject_on_worker_lost which is already the default behaviour

@enochtangg enochtangg requested review from a team as code owners April 4, 2025 17:42
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Apr 4, 2025
@enochtangg enochtangg merged commit 6808a68 into master Apr 4, 2025
50 checks passed
@enochtangg enochtangg deleted the migrate-hybridcloud-taskworker branch April 4, 2025 19:27
andrewshie-sentry pushed a commit that referenced this pull request Apr 8, 2025
This work is required to migrate tasks from celery to the new taskbroker
system. The sentry option will be used to control the rollout of these
tasks. The full migration plan is describe in this
[document](https://www.notion.so/sentry/Rollout-Planning-1bd8b10e4b5d80aeaaa7dba0efca83bc).

Notable changes/callouts
Most of relocation tasks use retry_backof, retry_backoff_jitter, and
soft_time_limit which taskworker does not support
LastAction (action taken when retries are exhausted) is set to discard
sentry.relocation.fulfill_cross_region_export_request uses
reject_on_worker_lost which is already the default behaviour
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants