Ok, I was mixing locking and priority. Duplicates handles the scenario for the same project being q'ed more than once.
Priority handles sequencing within the q. Locking handles exclusive build rights to a q (again sequencing q's here). So if I dont lock projects in differnt q's can run in parallel (multitasking on the cpu,memory..) Same is not true for projects within a q, i.e; if I dont provide a sequence(priority) projects wont run in parallel. They will just follow a natural FIFO path. Right ? Siddharth On Wed, Mar 11, 2009 at 1:34 PM, Matt Chatterley <[email protected]>wrote: > > > 2009/3/11 jonty s <[email protected]> > >> *Lock Tag* >> >> Will the config catch a circular lock ? >> >> Why do we have lock's, dont priority handle the sequencing problem ? >> >> What if I lock B when running A, but instead prioritize B to run earlier >> than A ? Do we handle this circular deadlock ? >> >> Please advice >> >> Siddharth >> > > I'll field this one :) > > If by circular you mean: > > Two Queues (1 and 2), set to lock each other - then yes. > > Priorities should execute within the context of a lock, e.g. > > Queue 1 locks, as a project starts - it will execute its projects, in > priority sequence, until it finishes, when it will release the lock. > > Queue 2 will then integrate (bit of a first-come-first served scenario here > - it's not 100% ideal). > > Essentially locking was put in to solve a scenario I ran up against where > we had a lot of projects, and certain ones needed complete isolation - e.g. > could not cross over with anything else. > > -- > Matt Chatterley > Mattched IT Ltd > http://www.mattchedit.com > UK Registered Company: 05861949 > >
