As I have tried to explain MUTLIPLE times, we do not have two workers fighting over
the same field. The threads are always separated correctly. We can have to processes
using
the same process_score, but that only affects the pid, generation, and sb_type. The
only thing
that matters in that case is the pid, and that is easily fixable, by moving it to the
worker_score
where it belongs.
Ryan
On Friday 27 July 2001 11:44, Jeff Trawick wrote:
> "Paul J. Reder" <[EMAIL PROTECTED]> writes:
> > Actually, it dawned on me that this is worse than I stated.
> >
> > There is no limit to processes joining a slot. If
> > perform_idle_server_maintenance deems it necessary to start more
> > processes, a new process can start within a slot where other processes
> > are still starting, but haven't yet grabbed all of the unused workers.
> >
> > Because there is no locking, more than one process can grab the same
> > worker slot. I have not looked to see what problems this can cause, but
> > two or more processes each starting a worker in the same slot can't be
> > good.
>
> This definitely sucks. The two workers in the same slot fight over
> the same status fields. This is a bug that needs to be fixed.
>
> We don't want more than one process taking over the slots for a
> process which is going away.
--
_____________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
Covalent Technologies [EMAIL PROTECTED]
-----------------------------------------------------------------------------
