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

Retry did not work after (104, 'Connection reset by peer') #252

Open
aakashb09 opened this issue Jun 21, 2023 · 0 comments
Open

Retry did not work after (104, 'Connection reset by peer') #252

aakashb09 opened this issue Jun 21, 2023 · 0 comments

Comments

@aakashb09
Copy link

aakashb09 commented Jun 21, 2023

I am using a reminders system using Redis, Celery Beat, RabbitMQ, Worker

Using Redbeat, I save a reminder in Redis, then Beat picks the reminder, puts it into a queue from where the worker picks it up, and sends the reminder.

My Redis instance is hosted by Upstash and since there are idle times >5 mins, Upstash resets my connection.

To mitigate this, I added a retry_period: -1 argument.

My questions are:

  1. Celery is configured to read from Redis every 5 minutes, this is defined in the DEFAULT_MAX_INTERVAL=300 right?
  2. I am assuming if I didn't see this
    logger.warning('beat: Retrying Redis connection in %s seconds...', retry_state.next_action.sleep)
    line anywhere in my logs, the retry has not happened, right?
  3. To not keep the connection idle, I have added a periodic task that repeats every 4 mins. However this doesn't solve the retry not happening, how best to go about this?

celery==5.2.7
celery-redbeat==2.0.0

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

No branches or pull requests

1 participant