High Collector CPU Use After Leap Second

Problem:

After a leap second occurs we start to see very high (100%) CPU use by the Sumo Logic Collector. 

Solution:

To address this issue you can run the following command (or similar) on the affected host to update the system clock.

service ntpd start

If this command fails to immediately address the problem an additional system reboot may be required.

Cause:

The issue being seen may be the result of a leap second bug within the Linux kernel of your host. A leap second is a one-second adjustment that is occasionally applied to Coordinated Universal Time (UTC) in order to keep its time of day close to the mean solar time. A defect in older Linux kernels could cause a livelock in the timer subsystem when the leap second was inserted resulting in the apparent high CPU use by the Collector process. More information regarding issues due to a leap second may be found through the following additional links.

• Resolve Leap Second Issues in Red Hat Enterprise Linux
• Preparing for the Leap Second