On Tue, Aug 4, 2009 at 5:22 PM, Parand Darugar<[email protected]> wrote: > I've been out of the loop on beanstalkd development for a while, > wanted to see what the latest is on persistence.
I have been busy with a contract project recently, but I am almost done with it. Then I'll finish up persistence and make a release. If anyone else wants to work on persistence right away, I am aware of two things that need to be done: 1. Allow beanstalkd to reserve arbitrary amounts of binlog space. http://github.com/kr/beanstalkd/issues#issue/14 2. Go over the actual format and make sure it is robust against errors in the data on disk, especially file truncation. http://github.com/kr/beanstalkd/issues/#issue/15 3. Add appropriate fsync calls, with optional throttling. http://github.com/kr/beanstalkd/issues/#issue/16 > Is persistence in the > latest version of beanstalkd from github production ready and > recommended? Not quite, because of the three things above. But if you trust your disks and power supply and don't generate big queues and don't mind binlog files being incompatible with the official release, go for it! :) > Apologies if this information exists somewhere already > but I wasn't able to find it. I'd also love a pointer to some usage > guides on how to enable/recover/examine persistence or some test cases > so I can build my own docs. There isn't much documentation. There is one command line option, -b, that controls binlog use. It takes the name of a directory where you want beanstalkd to look for and save binlog files. kr --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
