threads/136345: Recursive read rwlocks in thread A cause deadlock with write lock in thread B

[Attilio Rao]

2009/7/16 Nick Esborn <nick at desert.net>:
>
>
> KDB, DDB, SCHED_ULE, and PREEMPTION are already turned on.  I will try
> FULL_PREEMPTION, INVARIANT_SUPPORT, INVARIANTS, and WITNESS, but when I
> first upgraded to 8.0, this server was unable to handle its workload with
> the INVARIANTS and WITNESS options turned on.

What do you mean with 'unable'? What was happening precisely?

> Also, it can take a while for it to become clear that the deadlock has
> occurred -- usually our monitoring picks it up when replication falls
> behind.  So it may be 15-20 minutes after the deadlock that I am able to run
> the above db commands.  Of course the thread will still be deadlocked.
>  Hopefully that doesn't reduce the value of the data obtained.

It should be still fine.

Thanks,
Attilio


-- 
Peace can only be achieved by understanding - A. Einstein