When timeout is reached (waiting for job result), client tried to acquire lock than do the job if succeed... Cycle. Deadlock lives shortly.
On 25 мар, 23:55, Les Mikesell <[email protected]> wrote: > gf wrote: > >> How does the updater distinguish itself from the rest? > > acquire() (atomic add). > > So a whole bunch of clients try to add some sort of key that you hope > are identical so all but one fail, the one that succeeds is supposed to > do some more work? What if its next step fails? > > -- > Les Mikesell > [email protected]
