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

bugfix in timestamp allocation for scheduler worker #33

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

frankdebot
Copy link

  • fixed bug: if there are more than 1 items to be processed with different timestamps in the past, then the scheduler will sleep() before it picks up the next item in the past. If messages keep on being queued faster then 1 per second then eventually the scheduler cannot keep up

frankdebot and others added 2 commits March 14, 2016 10:58
- fixed bug: if there are more than 1 items to be processed with different timestamps in the past, then the scheduler will sleep() before it picks up the next item in the past. If messages keep on being queued faster then 1 per second then eventually the scheduler cannot keep up
so it always gets the oldest timestamp before now.
Timestamp should be defined for enqueueDelayedItemsForTimestamp
@rolfvreijdenberger
Copy link

Hi. in our high traffic applications we encountered bugs in the way the scheduler works if it was temporarily disabled. If there are more items in the past to be processed, the non-patched version picks up 1 item and sleeps(1) till it picks up the next. This seems to be because of a logical bug. this patch fixes that.

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