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
{{ message }}
This repository has been archived by the owner on Mar 31, 2021. It is now read-only.
We have a special case where we want an event to get fired after Now + X second( where X is less than 60 second).
Going through the code i figured out that there is a ScheduleScanner which runs every 1 minute to scan the buckets to be processed. So if this scan for the bucket happened, and my events is added after this scan , the events is not fired , which makes sense as per the current implementation.
What i am suggesting , when we are adding events , can we have a lookup if the events bucket is already scanned then schedule this event as well for processing.
The text was updated successfully, but these errors were encountered:
I second the above. I noticed events that fall into this category: they are never fired.
Regarding your suggestion, if it falls into this category, we could schedule it on the very next bucket which is (T+1) min at 0th second on the next tick (if its not really that urgent). Or we could override and add the event to the current bucket that is currently running.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a special case where we want an event to get fired after Now + X second( where X is less than 60 second).
Going through the code i figured out that there is a ScheduleScanner which runs every 1 minute to scan the buckets to be processed. So if this scan for the bucket happened, and my events is added after this scan , the events is not fired , which makes sense as per the current implementation.
What i am suggesting , when we are adding events , can we have a lookup if the events bucket is already scanned then schedule this event as well for processing.
The text was updated successfully, but these errors were encountered: