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

Use an explicit kombu.Connection while sending authority tasks #9408

Merged
merged 1 commit into from
Mar 20, 2025

Conversation

marcospri
Copy link
Member

Celery doesn't make it easy to dynamically send tasks to different brokers without statically defining them beforehand.

Create an explicit connection to the right authority broker instead

See: celery/celery#4284

Celery doesn't make it easy to dynamically send tasks to different
brokers without statically defining them beforehand.

Create an explicit connection to the right authority broker instead
annotation.id,
annotation.authority,
)
with Connection(authority_queue_config.broker_url) as connection:
Copy link
Member Author

Choose a reason for hiding this comment

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

Using the context manager here to call .release()

@marcospri marcospri requested a review from mtomilov March 20, 2025 11:26
Copy link
Contributor

@mtomilov mtomilov left a comment

Choose a reason for hiding this comment

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

Looks good 👍

@marcospri marcospri merged commit b183936 into main Mar 20, 2025
11 checks passed
@marcospri marcospri deleted the authority-queue-connection branch March 20, 2025 12:23
Copy link

sentry-io bot commented Mar 27, 2025

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

  • ‼️ AccessRefused: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile. h.tasks.annotations.publish_annotation_event_fo... View Issue

Did you find this useful? React with a 👍 or 👎

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.

2 participants