Does it also happen with beanstalkd 1.2? I believe some of the various timeouts are still buggy, due to the code's habit of rounding deadlines to whole numbers of seconds.
As soon as I've got my binlog patch pushed, I'll fix the timeout stuff once and for all by storing deadlines internally at microsecond resolution. (That will also pave the way for a possible future protocol extension for sub-second time intervals.) kr On Sun, Apr 12, 2009 at 1:58 AM, tekker <[email protected]> wrote: > > Hi, > > I've compiled beanstalkd 1.3 against libevent-1.4.9-stable. I'm using > the beanstalk-client ruby gem to process jobs. What happens now every > once in a while is that a job gets put in the queue successfully, > returns a job id, but the worker is waiting for about 4 minutes doing > nothing (no other jobs are processed and the submitted job is kept at > read state). After about 4 minutes the worker finally continues to > reserve the job and processes it. Both the beanstalkd and client are > on the same machine. There are 5 workers running, and all exhibit the > same behaviour at the same time (so all 'freeze' for 4 minutes and > then continue to reserve jobs). The client is using a plain > > loop do > job = POOL.reserve > ... > end > > to work the queue. Memory usage is normal so nothing strange there. > Any ideas what it could be? > > Many thanks! > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
