3 ms·
Only tangential but still interesting. During the infamous leap second fiasco of Java in 2012 which brought down all JVM servers by saturating the CPU, I saved
by yuchi 5y ago
Only tangential but still interesting.
During the infamous leap second fiasco of Java in 2012 which brought down all JVM servers by saturating the CPU, I saved the day because I was reading about it here on HN while my colleagues were struggling to undestrand why all our environments stopped working.
It took me a few minutes to realize that we were indeed hit by what I just read, look at ten of my colleagues each closely inspecting logs at different ssh sessions, and gleefully give them a precise description of the problem, an approach to verify it and a solution, adding “it’s all over the news guys, you should keep yourself updated”.