From: Raghavendra D Prabhu
Date: July 1 2012 10:52am
Subject: Re: most mysqld instances running with 100% CPU
List-Archive: http://lists.mysql.com/mysql/227758
Message-Id: <20120701105203.GA30607@Xye>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi"

--Qxx1br4bt0+wmkIi
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,


* On Sun, Jul 01, 2012 at 12:44:42PM +0200, Reindl Harald <h.reindl@theloun=
ge.net> wrote:
>i notice since this night all mysqld instances
>suing innodb are running at very high CPU, there
>is nothing in the mysqld-log and after restarting
>the service the same again
>
>i do not think this has to to with the reason taking
>back 5.5.25 becasue no disk-IO, i more doubt this
>has to do with the time-correction-second (not sure
>how to translate "Schaltsekunde" to english) because
>it started late at night
>______________________
>
>http://dev.mysql.com/doc/refman/5.5/en/news-5-5-25a.html
>
>BTW: since there are announcements of new versions of
>mysqld it is very rude take them back without any
>announcement and put after weeks some lines in the old
>changelog which nobody reads after rollout
>
>however, as said, i doubt this is not the problem
>

It has to do with  http://bugs.mysql.com/bug.php?id=3D65778=20

More analysis here:


http://blog.mozilla.org/it/2012/06/30/mysql-and-the-leap-second-high-cpu-an=
d-the-fix/=20
http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates=
-of-linux-server-crashes-during-a-leap-second

It is more of a linux kernel bug (affecting RHEL >=3D6 in the=20
enterprise kernels category).



Regards,
--=20
Raghavendra D Prabhu (TZ: GMT + 530)=20
Call: +91 96118 00062
mailto:raghavendra.prabhu@stripped
Percona, Inc. - http://www.percona.com / Blog: http://www.mysqlperformanceb=
log.com/
Skype: percona.raghavendrap
GPG: 0xD72BE977

--Qxx1br4bt0+wmkIi
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQEcBAEBAgAGBQJP8CvTAAoJEKYW3KHXK+l3qeQH/RV9oc0fP6+bPTa7msZK7Kfw
g6zmF9rsws0eWDt8USCfVJgAgiKpk8lM1vvfYymdJnbFiO3ne+NZZHmX6a+usJnY
+BTnjcRRWMagMGOeWb01giVIRWHUPQDNdoU7NjDnFFhnoyhC0/+3PJZ4XFJIFi6H
eqGduw9wgyJOIWGpjIRUyQKm4X+W9VN+zqyfrp49Q9xSn/vvj8pxxAIW/1XceAzC
NCqOr4IeAzEA8ruX5n3LwHQl54Ufk/esP+O55v6dWWjOPDTBfIYcTnxFhtTz/BNt
LvinbefufsnPZ6jEa8rS8AV66W40U23qYVniN1+SzE2mHYW6PLQ53YRkXwAdsKg=
=VnPl
-----END PGP SIGNATURE-----

--Qxx1br4bt0+wmkIi--