I can say that the job scheduling will work this way. I am not doing that in production though. I have this setup for development where the developers run their own instance of Turbine. The developers and our test server all share the same database.
I don't think that you will be able to submit a job from one instance and it be picked up from another. The scheduling service will load the scheduled jobs from the database on startup. I don't think that the service will check the table again after startup. I really can't say anything about the id broker though. I use Oracle sequences for id generation. That should be a relatively easy thing to check for though. > -----Original Message----- > From: Kevin Rutherford [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 16, 2002 12:14 PM > To: '[EMAIL PROTECTED]' > Subject: Multiple Turbine servers > > > I just wanted a sanity check to make sure that we are not > using Turbine inappropriately. > > We have a distributed system with two web servers and > multiple "job servers", all of which are running their own > instance of Turbine (roughly version 2.1 beta 2). All of the > instances of Turbine connect to the same database. > > This all seems to be working OK, but I am concerned about > whether Turbine/Torque is designed to be used this way. For > example, will the ID brokers conflict with each other in any > way? Are there any known problems with running multiple > instances of Turbine, all talking to the same database? > > Thanks, > > Kevin > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
