So once again I am a volunteer to work on this. Same question: has there been any progress? I have already forked the github repo and will be submitting pull requests soon.
I think there is a simple change that can be made to move this in the right direction. I propose that we add support for multiple binlog dirs so the binlogs can exists somewhere on a shared file system for disater recovery. Then we can work on replicating hte bin log itself. As for the architecture I think I will just ignore it and in the event that the format gets fixed then cross architecture servers will be able to replicate. Does this sound like a good approach? Thanks On Wednesday, January 4, 2012 5:21:04 PM UTC-7, Keith Rarick wrote: > > On Wed, Jan 4, 2012 at 9:48 AM, Jesse Sanford > <[email protected]<javascript:>> > wrote: > > I would like to pick up this project. Keith can you point me at any (if > any) > > code spikes that have been done in this direction? > > I don't know of any, but I'm happy to answer questions and do > code review. Is there anything else you need to get started? > It'd be good to briefly talk about the design (especially as it > impacts the user experience of beanstalkd) before actually > writing code. > > The current on-disk format is different on different hardware, > since beanstalkd just copies bytes out from the job struct. > This means that, for example, replaying the log from a 32-bit > machine on a 64-bit machine won't work. (In hindsight, it > would have been better to design an architecture-independent > format; if the format ever changes again, I'll want to do that.) > > kr > > -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/beanstalk-talk/-/qjXv2gy1AxkJ. 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.
