Hey Ryan,
We have jobs that are triggered via cron. One of these is a management task creates / destroys various expensive (time/computationally wise). This task takes a varying amount of time depending on how loaded our servers are so, we queue it. However, without locking there is a possibility that there might still be the same task more than once, which would generally not be a good thing (™).
I was interested in how others solved the same issue and also why they needed to :-)
I'll tidy up the code sometime soon and release if there is interest!!
Russ
Rainforest |
+1-650-919-3216 |
rainforestqa.com
> You received this message because you are subscribed to a topic in the Google Groups "queue_classic" group.
> To unsubscribe from this topic, visit
https://groups.google.com/d/topic/queue_classic/xhFqThkfCKI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
queue_classi...@googlegroups.com.