Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Jul 2009 10:56:55 -0700
From:      Nick Esborn <nick@desert.net>
To:        Attilio Rao <attilio@freebsd.org>
Cc:        freebsd-threads@freebsd.org
Subject:   Re: threads/136345: Recursive read rwlocks in thread A cause deadlock with write lock in thread B
Message-ID:  <C3A90BDA-0B42-4CDA-9193-AA27815CFE3B@desert.net>
In-Reply-To: <3bbf2fe10907161053x3b6aa60dneb8dbd5217b4cb03@mail.gmail.com>
References:  <200907152140.n6FLe42l045879@freefall.freebsd.org> <3bbf2fe10907160526l2f066698qce8a5e77aee6366b@mail.gmail.com> <3bbf2fe10907160548l74de896bka609de7a9a994899@mail.gmail.com> <6E6A9516-6C69-4E41-803C-FE5F126F402C@desert.net> <3bbf2fe10907161053x3b6aa60dneb8dbd5217b4cb03@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--Apple-Mail-25-1024360403
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit


On Jul 16, 2009, at 10:53 AM, Attilio Rao wrote:

> 2009/7/16 Nick Esborn <nick@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?

System time would rise during periods of peak demand, and the system  
would quickly fall behind on its workload of queries.

However, I have some hardware I can dedicate to this, and only run the  
one MySQL data set which exhibits this problem.  That should be enough  
of a workload reduction to allow the server to keep up even with all  
the above options turned on.

-nick

>
>> 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

--
nick@desert.net - all messages cryptographically signed


--Apple-Mail-25-1024360403
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
content-transfer-encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkpfaegACgkQw1bX5UNr2AB6qACgvzbhe6F7Csn7uHlsREMn4V/X
YT0AniKg3hfVQr+ehpZ5+LUxAihxVGpm
=zL/+
-----END PGP SIGNATURE-----

--Apple-Mail-25-1024360403--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C3A90BDA-0B42-4CDA-9193-AA27815CFE3B>