Hello, We are using one beanstalkd server and there are several workers which watch more than one tube at a time. Our main application is the producer which submits jobs to the beanstalkd server on different tubes.
Something like the following: <--------- Worker 1 with tubes worker1_unique_tube1, worker1_unique_tube2,worker1_unique_tube2 Application ---------> BeanstalkD Server <--------- Worker 2 with tubes worker2_unique_tube1, worker2_unique_tube2,worker2_unique_tube2 <--------- Worker 3 with tubes worker3_unique_tube1, worker3_unique_tube2,worker3_unique_tube2 The application can submit a job using any of the tube and thereby that job should be picked up by the worker who is watching that tube. This does happen, though for e.g if the application submits 5 jobs for the tube "worker1_unique_tube1" and at this stage if the Worker1 is free, it reserves the first job that is ready in that tube and completes it, however it is noticed that the other 4 jobs which were submitted remain in READY state for ever unless we manually re-queue them in that tube. So the question is, does beanstalkd server lose the other jobs from the READY queue of the tube without them even getting started? -Manish -- 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.
