Since beanstalk allows one to insert jobs at various priorities, it is possible for jobs with higher priorities keep getting added faster than they can be processed, which would result in lower priority jobs becoming starved. Is there anything available that can help prevent job starvation, e.g. a timeout such that once a job has been in the tube for a certain amount of time it is bumped to the head of the queue, or its priority gradually raised so it slowly bubbles to the top?
I don't see any way of detecting this at the application layer either, as it isn't easy to peek into a tube to see any job other than the one at the head of the queue. If it could peek at the *lowest* priority job to check its insertion date (and possibly reprioritize it), then the application could implement its own anti-starvation policy. Thoughts? Have others encountered this scenario in the past? -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
