Blender ID queue flushing should use smarter timing #53539

Closed
opened 2017-12-11 09:55:44 +01:00 by Sybren A. Stüvel · 3 comments

Currently when something is queued nothing else happens. The queue is flushed by our cron job running every 5 minutes, and that's it. It would be nice to have a more frequent check when the first failed item is being queued so that a 1-second downtime doesn't cause a 5-minute lag.

Currently [when something is queued](https://sentry.io/blender-institute/blender-id/issues/415722230/) nothing else happens. The queue is flushed by our cron job running every 5 minutes, and that's it. It would be nice to have a more frequent check when the first failed item is being queued so that a 1-second downtime doesn't cause a 5-minute lag.
Author
Owner

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren
Sybren A. Stüvel self-assigned this 2017-12-11 09:57:05 +01:00
Author
Owner

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Author
Owner

Implemented in c83c12cb44 and following commits.

Implemented in c83c12cb44fbc03a880ee53999c0593485bef29a and following commits.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/blender-id#53539
No description provided.