Skip to content
This repository has been archived by the owner on Mar 31, 2021. It is now read-only.

What if i want to fire an event which is less than 60 seconds from now and the bucket scan already happened for this event? #48

Open
jgudbhav opened this issue Jun 10, 2020 · 1 comment

Comments

@jgudbhav
Copy link

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.

@vvavepacket
Copy link

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants