[dijit]

Last time this happened I was the only sysadmin in a fairly small ecommerce company dependant on mysql.

The leap second caused our databases to all peg at 100% CPU/memory consumption..

Given the wide adoption and commercial nature of mysql, I can't begin to imagine how systems designed to be super precise will handle this..

[mootothemax]

The leap second caused our databases to all peg at 100% CPU/memory consumption.

I remember being utterly ridiculed that weekend, after swearing about fixing servers on Facebook.

It didn't take long for apologies to arrive on the following Monday, once the corporate sysadmins logged in and saw anything Java-based had also massively, massively failed.

It's the small (and petty!) victories.

[kbd]

> anything Java-based had also massively, massively failed.

What was the error in Java?

[valleyer]

What was the root cause of the problem?

[ars]

It was a linux kernel bug, not a MySQL bug: https://blog.mozilla.org/it/2012/06/30/mysql-and-the-leap-se...

[soup10]

if(seconds>60) while(1) malloc(1);

[calineczka]

I experienced similar problems in other kinds of applications as well. 100% cpu usage until restart.

[jerf]

If you experience that problem this year, this supposedly can be fixed without even restarting the process by running "date -s now". I say "supposedly" because I can't validate, but based on my reading of the problem and why that works, I have no reason to believe it won't.