You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to 5.2.6 we noticed an unexpected behaviour in our metrics for one of queues. Right after the upgrade, queue delays went up to hours, which didn't reflect the reality on the enqueued items.
The peculiarity on this queue is that we schedule jobs for many days in the future under it. It also has a higher chance of jobs failing and being retried.
We believe the changes introduced in cfe53e5 to be culprit. Before these changes, we would get a new enqueued_at value when it was re-enqueued. Now, the original value is kept.
Is this side-effect intended? If so, then we may look to alternatives. Any hint on how to handle it now, would be greatly appreciated!
The text was updated successfully, but these errors were encountered:
Ruby version: 2.5.5
Sidekiq / Pro / Enterprise version(s): Sidekiq Enterprise 5.2.6
After upgrading to
5.2.6
we noticed an unexpected behaviour in our metrics for one of queues. Right after the upgrade, queue delays went up to hours, which didn't reflect the reality on the enqueued items.To calculate the delay, we use this formula:
The peculiarity on this queue is that we schedule jobs for many days in the future under it. It also has a higher chance of jobs failing and being retried.
We believe the changes introduced in cfe53e5 to be culprit. Before these changes, we would get a new
enqueued_at
value when it was re-enqueued. Now, the original value is kept.Is this side-effect intended? If so, then we may look to alternatives. Any hint on how to handle it now, would be greatly appreciated!
The text was updated successfully, but these errors were encountered: