Leap second bug found to be Linux issue, not Cassandra.
Several articles have been published recently , ,  that have incorrectly indicated that Cassandra had a “leap second” bug that caused some problems for many high-profile sites running Cassandra. As a point of fact, it was a Linux bug that caused the issue.
The challenge was that when troubleshooting the problem, some applications such as Cassandra, MySQL, Hadoop, Elastic Search, and others showed extremely high CPU consumption, which led people to initially believe they were the problem, when in actuality they were only a symptom.
The good news is that the power of the open source community led to very fast information sharing and resolution!
If you have any questions, let us know.