We've been using beanstalkd for a year or two now with really very minimal problems. That said we've never had one of our beanstalkd servers totally die (knocking on wood). We have had the process crash once or twice and when we restarted it it read the binlogs and started back up without incident.
The way our setup is -- we have 3 beanstalkd servers all identical and all to be used for holding the same tubes. Then in our producers we randomly distribute jobs to one of the 3 servers -- skipping over any server if it happens to be down. On the consumer side we have 3 servers all running the same consumers, but pointed at particular servers. so consumer A points to beanstalkd server A, consumer B to beanstalkd server B, and so forth. In this way we are able to reliably keep job production running even in the event of a beanstalkd server failing, and we are similarly able to keep consumption going in the same situation. We monitor the backlog in each of our tubes on each server to make sure the consumers are still running and able to keep up with production. Hope it helps! --chad On Tue, Aug 2, 2011 at 3:03 PM, rstradling <[email protected]> wrote: > I am looking to use beanstalk on our next project and have a lot of > questions about reliability and/or how others handle it. The reason I > am here is I am curious if binlogs work as well. I have seen a decent > amount of posts saying they do and some saying they are experimental. > > But when I think of this I am looking at > Is sending of the job reliable to the server? I believe this is a no > and the best way to handle this would be via a master slave type > arrangement where they both watch the same queue. The slave would > monitor the master and if the master is down would start processing > the queue. Is that what people would recommend? > > Are tubes fault tolerant? If the machine with the tubes fail what > happens? How is redundancy handled for this? I believe that is where > bin logs enter the equation. Correct? > > I appreciate any help or advice. > > Thanks, > Ryan > > -- > 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. > > -- 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.
