Leap Second on 6/30/2015 Caused mysqld Process To Consume CPU
337
post-template-default,single,single-post,postid-337,single-format-standard,bridge-core-3.0.1,qodef-qi--no-touch,qi-addons-for-elementor-1.5.3,qode-page-transition-enabled,ajax_updown,page_not_loaded,,vertical_menu_enabled,side_area_uncovered_from_content,qode-theme-ver-28.7,qode-theme-bridge,disabled_footer_top,qode_header_in_grid,wpb-js-composer js-comp-ver-6.8.0,vc_responsive,elementor-default,elementor-kit-6

Leap Second on 6/30/2015 Caused mysqld Process To Consume CPU

01 Jul 2015 Leap Second on 6/30/2015 Caused mysqld Process To Consume CPU

Posted at 08:35h in Bugs, MySQL, Programming, Unix by

This morning I got a notification that mysqld was consuming on average 35% of the CPU on one my servers. This was strange because this particular server doesn’t even use MySQL regularly. It’s there only to serve a rarely used legacy table. A quick look with “show processlist” confirmed that there were no queries running. After a bit of search, I found the solution here:

https://blog.mozilla.org/it/2012/06/30/mysql-and-the-leap-second-high-cpu-and-the-fix/

The solution is to run a short script that sets the correct time. Basically, the cause was the leapsecond that was added at midnight UTC. Here is a screenshot showing when mysqld starting consuming CPU – exactly at midnight UTC.

Screen Shot 2015-07-01 at 8.11.15 AM



Mastodon