this is the second time the issue is posted and yet I can't find a way to reproduce it.... It's true that I'm running two scheduler processes on the same machine vs one scheduler on on machine and the other on another separate one, but as far as the "assign" algorithm is concerned, as long as there are two scheduler_workers rows, nothing should change. Just as a proof, can you confirm that when you start two schedulers on the same server you observe the same behaviour ?
On Friday, April 5, 2013 8:47:58 PM UTC+2, Yoel Benitez Fonseca wrote: > > El 5.4.2013 6:47 am, Niphlod escribió: > > what db are you using ? > > postgres, is the same database shared between servers > > > > > On Friday, April 5, 2013 6:24:13 AM UTC+2, Yoel Benitez Fonseca wrote: > >> > >> i have this setup: > >> > >> 2 severs with the same web2py & app installed, each of then run a > >> scheluder worker > >> > >> the problem is that only one of then get jobs, and in > >> db.scheluder_worker the one with do all the work is the only with > >> true > >> in is_ticker field, i just the 2 of em cooperate and pickup the > >> available jobs. > >> > >> P.D: got them in diferent's groups and randomly assing task to the > >> groups. > >> > >> -- > >> Yoel Benítez Fonseca > >> Tel: 573400 > >> > > -- > Yoel Benítez Fonseca > Tel: 573400 > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
