[Swift-devel] current workers < 0 ?

[Mihael Hategan]

I suspect the issue was introduced by the addition of multiple coasters
per node. The manager expects one worker, but gets 16 instead. 

On Wed, 2009-02-25 at 22:29 -0600, Allan Espinosa wrote:
> It still has the same issues.  It subtracts too much when a task if finished.
> 
> Also, observing the LRM queue, i see swift  creating 18-20 "make
> coaster" requests (4 at start then 16-18 after 5 mins).  with a 16
> coastersPerNode you get a 320 processor allocation.  this more than
> MAX_WORKERS~256 and the max score possible from my sites.xml (102 max)

Regarding MAX_WORKERS, that probably suffers from the same problem, in
that it may request less than 256 workers, but given that each request
means 16 workers, the end result may be different than what's expected.

However, MAX_WORKERS was introduced merely to limit damage in case the
code is bad and it doesn't otherwise put an upper bound on the limit of
worker requests (/jobs in the queue).